Allow disabling claude.ai connectors from Claude Code settings

Resolved 💬 3 comments Opened May 12, 2026 by syncrahq Closed May 23, 2026

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!

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗