Add "Disable MCP" option to `/mcp show` interactive menu

[Licantrop0]

Currently, you can disable an MCP server using the /mcp disable <server-name> command, but the /mcp show interactive menu only exposes "add" and "delete" options. The "disable" action is missing from the menu, making it less discoverable.

Proposed solution

Add a "Disable MCP" option to the /mcp show interactive menu alongside the existing "add" and "delete" commands. This would allow users to disable MCP servers directly from the interactive menu without needing to know the /mcp disable <server-name> command.

This benefits users by:

• Making MCP management more discoverable and consistent — all MCP operations (add, delete, disable) would be accessible from the same interactive menu
• Reducing friction for users who prefer the interactive menu over typing commands
• Providing a more complete interactive experience

Example prompts or workflows

1. User types /mcp show → sees the list of MCP servers → selects a server → sees options: Add, Delete, Disable → selects "Disable" → server is disabled
2. User wants to temporarily disable a noisy MCP server without deleting it → opens /mcp show → picks the server → disables it from the menu
3. User is troubleshooting an MCP connection issue → uses /mcp show to quickly disable/re-enable servers from the menu without remembering the slash command syntax

Note: Enable option is present for disabled servers instead of Disable.

Additional context

You can already disable an MCP server via the command /mcp disable <server-name>

But the /mcp show menu does not include a "Disable" option, only add/delete are available:

[diegomsft]

Just in general, Claude Code UX around CLI menus is way more refined. Why should I write commands instead of interacting with the results of /plugins, /mcp and so on?

[DrEsteban]

A couple of additional UX details from my own use that seem worth capturing here:

• The pain is not just that enable/disable is missing from the interactive MCP view; it is also that /mcp and /mcp show are transient. Once I exit that screen, I can no longer reference the full on-screen list while issuing follow-up commands.
• That means the current workflow often becomes: open /mcp, inspect the list, memorize the exact server name, exit, then run /mcp enable <name> or /mcp disable <name>. That is a lot of friction for a routine toggle operation.

So I strongly agree that in-view enable/disable is the right fix.

If that cannot happen immediately, a useful fallback would be: a persistent/non-modal rendering of the MCP list so it remains visible in the terminal after the command completes. The direct toggle is still the preferred solution, but the transient nature of the current view is a related usability issue that contributes to the friction.

[benc-uk]

This seems extremely low hanging fruit from a UX perspective, and would make a huge difference
The MCP menu could do so much more

[RossTarrant]

Hey @Licantrop0, thanks for the suggestion.

I can confirm this functionality will be available in the next release of Copilot CLI, you will be able to use the space key to quickly enable/disable MCP servers from the list view.

Please keep an eye on our releases page to keep up to date on when that drops.