claude-code - 💡(How to fix) Fix [FEATURE] Support disabling claude.ai MCP connectors at the project level [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#45158Fetched 2026-04-09 08:11:57
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Author
Timeline (top)
labeled ×2commented ×1renamed ×1

Root Cause

I have two repos:

  1. Internal ops repo — I use Slack, Linear, and Google Calendar connectors to manage tasks and communicate with teammates directly from Claude Code.
  2. 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.

Code Example

{
  "cloudMcpConnectors": "disabled"
}

---

{
  "disabledCloudMcpConnectors": ["Slack", "Linear", "Google Calendar"]
}
RAW_BUFFERClick to expand / collapse

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

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:

  1. Internal ops repo — I use Slack, Linear, and Google Calendar connectors to manage tasks and communicate with teammates directly from Claude Code.
  2. 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

extent analysis

TL;DR

To address the issue, consider adding a project-scoped setting in .claude/settings.json to disable cloud MCP connectors, such as "cloudMcpConnectors": "disabled" or specifying disabled connectors with "disabledCloudMcpConnectors": ["Slack", "Linear", "Google Calendar"].

Guidance

  • Evaluate the proposed solution of adding a "cloudMcpConnectors": "disabled" or "disabledCloudMcpConnectors": ["list of connectors"] setting to .claude/settings.json for disabling cloud MCP connectors at the project level.
  • Test the alternative solutions mentioned, such as setting ENABLE_CLAUDEAI_MCP_SERVERS=false or using permissions.deny: ["mcp__claude_ai_*"], to understand their limitations and why they do not fully address the issue.
  • Consider the impact of disabling cloud MCP connectors on productivity and project management workflows, especially in repositories where these connectors are essential.
  • Review the use case examples provided to ensure the proposed solution aligns with the desired outcome of having a clean, focused coding environment in specific projects.

Example

{
  "cloudMcpConnectors": "disabled"
}

or

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

Notes

The effectiveness of the proposed solution depends on the implementation details of claude.ai MCP connectors and how settings in .claude/settings.json are interpreted by the system. It's crucial to test these settings in a controlled environment before applying them to critical projects.

Recommendation

Apply the workaround by adding the proposed setting to .claude/settings.json, as it directly addresses the need to disable cloud MCP connectors at the project level, thus potentially improving productivity by reducing clutter and noise in the coding environment.

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