claude-code - 💡(How to fix) Fix Allow disabling claude.ai connectors from Claude Code settings

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…

Root Cause

For a user with ~1000 sessions/month and 4 unused connectors, this is ~8M tokens/month of dead schema in the cached prefix. The CodeBurn community tool (npx codeburn optimize) flags this category as a top-3 cost driver for heavy CC users.

Thanks!

Fix Action

Fix / Workaround

  • disabledMcpjsonServers in settings.json only targets explicit .mcp.json / claude mcp add servers, not claude.ai-synced connectors.
  • No env var (e.g. CLAUDE_DISABLE_CONNECTORS) or CLI flag documented.
  • No way to scope-disable per-project vs global from the CC side.
  • The only workaround is disconnecting them in the claude.ai web UI, which also disables them in claude.ai chat.

Code Example

{
  "disabledConnectors": ["claude_ai_Canva", "claude_ai_Gmail"]
}
RAW_BUFFERClick to expand / collapse

Problem

claude.ai-synced connectors (Canva, Gmail, Google Drive, Google Calendar) auto-load into every Claude Code session when the CLI is authenticated with a claude.ai account. Each adds ~2K tokens of tool schema to the cached prefix, paid on every turn.

Users may legitimately want these connectors active in claude.ai web chat but disabled in Claude Code to reduce per-session token overhead — especially heavy CC users with hundreds of sessions/month.

Current state

  • disabledMcpjsonServers in settings.json only targets explicit .mcp.json / claude mcp add servers, not claude.ai-synced connectors.
  • No env var (e.g. CLAUDE_DISABLE_CONNECTORS) or CLI flag documented.
  • No way to scope-disable per-project vs global from the CC side.
  • The only workaround is disconnecting them in the claude.ai web UI, which also disables them in claude.ai chat.

Request

Add a settings.json key to disable claude.ai-synced connectors specifically. Suggestions:

  • Extend disabledMcpjsonServers to match connector names like claude_ai_Canva, claude_ai_Gmail, etc.
  • Or add a new key, e.g.:
{
  "disabledConnectors": ["claude_ai_Canva", "claude_ai_Gmail"]
}

Scope: should work at both global (~/.claude/settings.json) and per-project (.claude/settings.json) levels.

Why this matters

For a user with ~1000 sessions/month and 4 unused connectors, this is ~8M tokens/month of dead schema in the cached prefix. The CodeBurn community tool (npx codeburn optimize) flags this category as a top-3 cost driver for heavy CC users.

Thanks!

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING