### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement I use claude.ai MCP connectors (Slack, Linear, Google Calendar, etc.) in several of my repositories for project management workflows. But in some repos — like a product I'm building — I want a clean, focused coding env

[FEATURE] Support disabling claude.ai MCP connectors at the project level

Status Closed — not planned

Maintainer reply ✓ Yes — localden

Activity 4 comments · opened Apr 8, 2026 · closed May 23, 2026

💡 Likely answer: A maintainer (localden, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

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

Problem Statement

I use claude.ai MCP connectors (Slack, Linear, Google Calendar, etc.) in several of my repositories for project management workflows. But in some repos — like a product I'm building — I want a clean, focused coding environment with no cloud connectors cluttering the tool list or consuming context window.

There's currently no way to disable claude.ai MCP connectors at the project level. The only MCP-related settings in .claude/settings.json (disabledMcpjsonServers, allowedMcpServers, deniedMcpServers) control locally-configured servers from .mcp.json, not cloud connectors.

Proposed Solution

A project-scoped setting in .claude/settings.json to disable cloud MCP connectors:

{
  "cloudMcpConnectors": "disabled"
}

Or more granularly:

{
  "disabledCloudMcpConnectors": ["Slack", "Linear", "Google Calendar"]
}

This should:

Prevent the connectors from loading in that project's sessions
Remove them from the /mcp panel (not just block tool calls)
Not affect other projects where the connectors are useful

Alternative Solutions

Setting ENABLE_CLAUDEAI_MCP_SERVERS=false in .claude/settings.json under env — has no effect, connectors still appear after fresh sessions.
Using permissions.deny: ["mcp__claude_ai_*"] — prevents tool calls but connectors still load, still appear in /mcp, and still consume context with their system instructions.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

I have two repos:

Internal ops repo — I use Slack, Linear, and Google Calendar connectors to manage tasks and communicate with teammates directly from Claude Code.
Product 1 (product repo) — a focused coding project where cloud connectors are irrelevant noise. I want only my local MCP servers and no cloud connectors because this project should not push anything to my company's repos.

Today if i open (2) and type /mcp, and see 14 claude.ai connectors I don't need. Their tool definitions inflate my context window and their system instructions add noise. I want to add one setting to .claude/settings.json and have a clean environment scoped to this project only.

Additional Context

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

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

v-amorim · 5 months ago

Up, what worked was disabling all claude.ai MCPs (which is not ideal):

// ~/.claude/settings.json
{
  "env": {
    "ENABLE_CLAUDEAI_MCP_SERVERS": "0"
  }
}

localden collaborator · 4 months ago

Thanks for the request. This is the same ask as #29368 (selectively disable claude.ai-synced connectors in Claude Code). Consolidating tracking there.

github-actions[bot] · 3 months ago

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.