Add enabled parameter to disable MCP servers by default in Claude Desktop config #1580
Replies: 2 comments
-
|
This seems to be a feature request for Claude Desktop. I am unsure of the best place to make that request, but this repository is for the development of MCP, the protocol itself, so I don't think your request will be seen here. 😕 |
Beta Was this translation helpful? Give feedback.
-
|
Many of the issues posted in this repo refer to at least one major MCP client (e.g., Claude Code or Claude Desktop). This issue is a subset of more of a general issue across most MCP clients. The process of handling many MCPs across many projects and different chat threads is very clunky right now. It is generally not easy to rapidly switch to different sets of MCPs/tools for different projects or chat threads. What are most people doing? Are they just enabling many MCPs globally or at least for entire projects (even if many chat threads don't need the MCPs), and thus clogging up their context window? The official GitHub MCP alone has nearly 100 tools. Besides much better interfaces in MCP clients for rapidly enabling/disabling MCPs/tools, the only other solution that I can think of is dynamic MPC/tool discovery at the per-chat thread level, where the LLM efficiently decides which MCPs/tools to load into the context window. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Currently, all MCP servers defined in
claude_desktop_config.jsonare automatically enabled when Claude Desktop starts. There's no native way to temporarily disable a server without completely removing its configuration from the file or manually toggling the MCP in the chat interface.This creates friction when:
Proposed Solution
Add an optional
enabledboolean parameter to the MCP server configuration that defaults totrue:{ "mcpServers": { "Arc SLURM MCP": { "enabled": true, "command": "uv", "args": ["run", "/path/to/server"], "env": {}, "transport": "stdio" }, "Arc Cloud Run MCP": { "enabled": false, // Disabled by default "command": "uv", "args": ["run", "/path/to/other/server"], "env": { "GCP_PROJECT_ID": "my-project" }, "transport": "stdio" } } }Benefits
Current Workarounds
Users currently must:
yqwith YAML conversion (as documented in [zudochkin/disable-claude-mcp](https://github.com/zudochkin/disable-claude-mcp))Related
Additional Context
This feature would align with standard configuration practices in other tools where services/plugins can be defined but selectively enabled.
Beta Was this translation helpful? Give feedback.
All reactions