[FEATURE] Disable individual claude.ai connectors at user scope, not just per-project

Priority: Medium – Would be very helpful
Feature Category: MCP server integration

Problem Statement

Org-provisioned claude.ai connectors arrive with the account. On a large enterprise account that can be ~90 of them. Most have never been authenticated, so they expose only authenticate / complete_authentication and cannot actually be called — but their tool names still sit in context in every session, in every project. In my case ~80 unauthenticated connectors cost roughly 2k tokens of tool names per session.

The only per-connector control is /mcp disable <server>, which writes disabledMcpServers into the per-project entry of ~/.claude.json. That's per-project by design, so switching a connector off everywhere means repeating the toggle in every project — and any newly-opened directory starts with it enabled again.

The only global control is the disableClaudeAiConnectors setting (and the ENABLE_CLAUDEAI_MCP_SERVERS env var), which is all-or-nothing: it also disables the handful of connectors I actively use.

So the available controls are "one connector, one project" and "all connectors, everywhere". There is nothing in between.

Proposed Solution

Honor disabledMcpServers / enabledMcpServers in the settings cascade at user scope (~/.claude/settings.json), merged with the per-project list, so a connector disabled at user scope stays disabled in every project — including directories opened for the first time. A scope flag on the existing toggle would make it discoverable:

/mcp disable <server> --global

Suggested precedence: a project-scope enabledMcpServers entry can re-enable a user-scope-disabled connector for one repo, so the global default stays overridable.

Alternative Solutions

• Repeat /mcp disable in every project — doesn't cover directories I haven't opened yet.
• Script the name list into every project entry of ~/.claude.json — what I do now. It grew my config from ~200KB to ~320KB across 55 project entries, and still misses any new directory.
• disableClaudeAiConnectors: true — disables the connectors I depend on.

Use Case Example

1. My org account provisions ~90 claude.ai connectors. I use 6 of them.
2. I clone a new repo and start a session. All ~90 are live again, and the unauthenticated ones' tool names land in context.
3. With a user-scope disable list, the ~80 I will never authenticate stay off everywhere, and the 6 I use keep working.

Related (not duplicates): #73682, #76010, #78314.

🤖 Generated with Claude Code