Improve MCP enable/disable UX in /mcp and /mcp show

[DrEsteban]

Describe the feature or problem you'd like to solve

Managing MCP servers is more cumbersome than it needs to be when I want to quickly enable or disable one from the CLI.

There are two related UX problems:

1. You cannot enable or disable an MCP directly from the /mcp or /mcp show view that lists configured MCP servers and available tools. To toggle one, I have to remember the MCP name, exit the view, and then run /mcp enable <name> or /mcp disable <name> manually.
2. The /mcp and /mcp show output is not persistent in the terminal after exiting the view. That means I cannot keep the list visible while issuing follow-up commands, so I also have to remember the exact MCP names from memory.

Together, these make a common workflow feel unnecessarily tedious.

Proposed solution

Preferred solution: allow enable and disable directly from the /mcp and /mcp show interactive view.

That would let users inspect the current MCP list, see which tools are available, and toggle a server in place without leaving the screen or memorizing names.

If that is not feasible immediately, a smaller improvement would be to make /mcp or /mcp show render persistent terminal output that remains visible after the command completes, so users can reference the list while running /mcp enable <name> or /mcp disable <name>.

This would benefit users by:

• Reducing friction for a common MCP management task
• Improving discoverability of enable/disable actions
• Removing the need to memorize exact MCP names during routine configuration changes
• Making the MCP management experience feel more consistent with other interactive CLI views

Example prompts or workflows

1. Run /mcp, review configured MCP servers, highlight one, and press the relevant action to disable it without leaving the view.
2. Run /mcp show, inspect which tools a server exposes, then re-enable a disabled server from the same screen after troubleshooting.
3. Temporarily disable a noisy or broken MCP while comparing available tools across servers, without having to remember exact names after closing the view.
4. If interactive toggling is not available yet, run /mcp show, keep the output visible in the terminal, and then issue /mcp disable <name> or /mcp enable <name> while referencing the on-screen list.

Additional context

There is already an open issue covering direct disable from /mcp show (#2956), but this request is intentionally broader:

• direct enable/disable from the MCP view is still the preferred solution
• persistent /mcp or /mcp show output would also meaningfully improve the current workflow, even if inline toggling is implemented later

[DrEsteban]

Closing this as a duplicate of #2956.

That issue already covers the core request to enable or disable MCP servers directly from the interactive MCP view. I added the extra UX details there about the transient /mcp and /mcp show views, the need to memorize exact MCP names, and the value of clearer in-view affordances / persistent output.