[Feature Request] Allow project-level control of claude.ai connectors via .mcp.json

[nick-youngblut]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Claude.ai connectors synced from a user's claude.ai account are loaded into every Claude Code session with no way to control them at the project level. The current options are:

1. All connectors everywhere — every project gets every claude.ai connector
2. No connectors anywhere — disable sync globally (e.g., via cachedGrowthBookFeatures.tengu_claudeai_mcp_connectors)
3. Per-session toggle — manually disable via /mcp each session (not persistent)

There is no middle ground. Users cannot specify which claude.ai connectors are relevant for a given project.
Why this matters:

• Tool clutter: Claude may attempt to use connectors that aren't relevant, wasting time and tokens on tool calls that don't help.
• Different projects need different tools: many tools are not relevant for certain projects

Proposed Solution

Allow .mcp.json (or .claude/settings.local.json) to disable specific claude.ai connectors at the project level.

Option A: Disable specific connectors in .mcp.json

{
  "mcpServers": {
    "claude.ai Asana": { "disabled": true },
    "claude.ai Slack": { "disabled": true },
    "claude.ai Notion": { "disabled": true }
  }
}

Option B: A dedicated key for claude.ai connector overrides

{
  "cloudConnectors": {
    "enabled": ["Arc Benchling MCP", "arc-google-sheets-mcp"],
    "disabled": ["Asana", "Slack", "Notion"]
  }
}

Option C: Allowlist mode — only load specified connectors

  "cloudConnectors": {
    "mode": "allowlist",
    "allow": ["Arc Benchling MCP", "arc-google-sheets-mcp"]
  }
}

Any of these would solve the problem. The key requirement is project-level scope — the same user should be able to have different connector configurations for different projects.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

A user has 15+ claude.ai connectors configured for use across claude.ai and Claude Code. They work across multiple projects:

• Project A (bioinformatics pipeline): Needs Benchling + Google Sheets connectors. Asana, Slack, and Notion connectors are irrelevant noise.
• Project B (internal web app): Needs Asana + Notion. Benchling connectors are irrelevant.
• Project C (data analysis script): Needs no connectors at all — pure coding task.

Today, all 15 connectors load into every session regardless of project context. The disallowedTools setting in .claude/settings.local.json can block tool invocation but doesn't prevent the connectors from loading and consuming context.

Additional Context

No response

[github-actions]

Found 3 possible duplicate issues:

1. Add setting to disable cloud MCP connectors from claude.ai #22301
2. Claude.ai MCP servers auto-injected into Claude Code without opt-in — causes OOM crashes on resource-constrained systems #20412
3. [Feature Request] Add project-exclusive MCP configuration option to disable user-level aggregation #21951

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]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[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.