Problem

Right now, when adding an MCP server to Claude Code, the server is automatically enabled and cannot be disabled without removing it entirely. This is not great when:

• Testing new MCP servers that may be unstable or broken
• Temporarily disabling servers for debugging purposes
• Managing multiple MCP servers where some should remain configured but not active (i.e. to serve as a comment for another MCP server since it's not possible to have comments in the JSON file, but you might want to have different examples on how to configure an mcp server).

Proposed Solution

Add an enable/disable toggle functionality for MCP servers that allows users to:

1. Add servers in disabled state: Option to add an MCP server without immediately enabling it
2. Toggle existing servers: Enable/disable servers that are already configured

Current Workaround

Currently, users must completely remove and re-add MCP servers to "disable" them, which:

• Loses configuration settings
• Requires remembering server setup details

The above creates friction in development workflows.