Feature request: client-side opt-out for claude.ai cloud MCP connectors

Problem

Claude Code CLI syncs feature flags from Anthropic's servers on every session start. The flag tengu_claudeai_mcp_connectors controls whether MCP integrations configured on claude.ai (web) are also injected into CLI sessions as deferred tools.

There is no reliable client-side way to disable this.

What I've tried

I created a SessionStart hook that sets tengu_claudeai_mcp_connectors: false in ~/.claude.json:

# SessionStart hook
python3 -c "
import json
with open('$HOME/.claude.json') as f:
    d = json.load(f)
d['cachedGrowthBookFeatures']['tengu_claudeai_mcp_connectors'] = False
with open('$HOME/.claude.json', 'w') as f:
    json.dump(d, f, indent=2)
"

This doesn't work because the server sync runs after the hook and overwrites the local value back to true.

Impact

• ~16.6k tokens (8.3% of context window) consumed by deferred cloud MCP tool names I never use in CLI
• Tools from computer-use, Claude_Preview, mcp-registry, and other cloud-configured integrations appear in every session regardless of local preference
• Power users who carefully curate their tool environment have no way to control this

Proposed solution

Add a setting in settings.json (or settings.local.json) that acts as a hard client-side override:

{
  "disableCloudMcpConnectors": true
}

This should take precedence over the server-synced feature flag, similar to how other settings in settings.json are respected locally.

Environment

• Claude Code CLI (latest)
• macOS Darwin 25.3.0
• Using Max plan with claude-opus-4-6

🤖 Generated with Claude Code