Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Per-connector toggle for claude.ai-synced MCP servers in Claude Code [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52762•Fetched 2026-04-24 10:40:11
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
jaypopatjaypopat
Participants
github-actions[bot]github-actions[bot]jaypopatjaypopat
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description Feature request: per-connector toggle for claude.ai-synced MCP connectors in Claude Code

Problem: MCP connectors enabled on claude.ai web (Gmail, Google Calendar, Google Drive etc.) are auto-synced into every Claude Code CLI session. Their tool names are injected into the deferred-tools list at session start, and some (like Nia) inject full MCP instruction blocks — hundreds of tokens per session — even when the user never intends to invoke them from CC.

Currently there's no way to scope these: disconnecting on claude.ai removes them everywhere, and settings.json has no disabledMcpServers or equivalent that matches mcp__claude_ai_* patterns. The permissions system can block execution but doesn't reclaim the context tokens consumed by tool names and instruction blocks.

Proposed solutions (either works):

  1. Settings-level exclusion list — support a disabledMcpServers array in ~/.claude/settings.json that accepts server name patterns (e.g. "mcp__claude_ai_Gmail", "mcp__claude_ai_Google_*", "apigcp"). Applied before tool-name injection at session start.
  2. Per-connector toggle on claude.ai — each connector gets a "Enable in Claude Code CLI" checkbox independent of its web-app availability.

Use case: I use Gmail/Calendar/Drive from claude.ai daily but never from Claude Code sessions on my dev machine. Right now I'm paying context overhead on every CC session for tools I'll never call there. For heavy users, this compounds across many sessions per day.

Environment Info

  • Platform: linux
  • Terminal: ghostty
  • Version: 2.1.119
  • Feedback ID: 8c2c31f9-349a-4ce7-912d-a6190251ea9a

extent analysis

TL;DR

To address the issue, consider implementing a settings-level exclusion list or a per-connector toggle to control which MCP connectors are synced into Claude Code CLI sessions.

Guidance

  • Review the proposed solutions and determine which approach best fits the requirements: a settings-level exclusion list in ~/.claude/settings.json or a per-connector toggle on claude.ai.
  • If implementing the settings-level exclusion list, ensure the disabledMcpServers array accepts server name patterns (e.g., "mcp__claude_ai_Gmail", "mcp__claude_ai_Google_*") to filter out unwanted connectors.
  • Evaluate the impact of the permissions system on the proposed solutions, as it currently blocks execution but doesn't reclaim context tokens consumed by tool names and instruction blocks.
  • Consider the use case and the potential benefits of reducing context overhead for heavy users.

Example

No code snippet is provided as the issue focuses on feature requests and proposed solutions rather than specific code changes.

Notes

The solution may require updates to the Claude Code CLI and claude.ai web application to support the proposed features. The exact implementation details are not provided in the issue.

Recommendation

Apply a workaround by implementing a settings-level exclusion list, as it seems to be a more straightforward solution that can be achieved through configuration changes. This approach allows for more flexibility in controlling which MCP connectors are synced into Claude Code CLI sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Per-connector toggle for claude.ai-synced MCP servers in Claude Code [1 comments, 2 participants]