Add setting to disable cloud MCP connectors from claude.ai

[wolfmanstout]

Feature Request

Add a setting to prevent Claude Code from automatically loading MCP servers that are configured as connectors in claude.ai.

Problem

MCP servers configured as connectors in a user's claude.ai account are automatically available in Claude Code sessions. These connectors may be useful in the claude.ai chatbot but not relevant in a coding context, where they consume context window space and clutter the tool list.

Currently the only workarounds are:

• Disconnecting the connector entirely in claude.ai (which also removes it from the chatbot)
• Using --strict-mcp-config --mcp-config '{}' to disable all MCP servers
• Toggling servers off per-session via /mcp

None of these allow a persistent Claude Code-specific preference while keeping the connectors active in claude.ai.

Proposed Solution

Add a setting (e.g. in ~/.claude/settings.json) to control whether cloud MCP connectors from claude.ai are loaded, such as:

{
  "mcpConnectors": "disabled"
}

Or more granularly, allow blocklisting specific connectors by name.

Use Case

A user has cloud MCP connectors set up for use with the claude.ai chatbot. These are not useful in Claude Code and add significant token overhead to every session's context window.

[github-actions]

Found 1 possible duplicate issue:

1. Claude.ai MCP servers auto-injected into Claude Code without opt-in — causes OOM crashes on resource-constrained systems #20412

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.