Support selective enable/disable of individual claude.ai MCP servers

Status Closed — not planned

Maintainer reply ✓ Yes — localden

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

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

Feature Request

Currently, the ENABLE_CLAUDEAI_MCP_SERVERS env var is all-or-nothing — it either enables or disables all claude.ai MCP servers in Claude Code. There's no way to selectively show/hide individual servers.

Use Case

Many users find only a subset of the claude.ai MCP servers relevant to their workflow (e.g., Slack and Sentry but not Figma or Airtable). Having 15+ servers cluttering the available tools list creates noise and confusion, especially for engineers who only need a few.

Proposed Solution

Support a per-server allowlist or denylist configuration, for example in ~/.claude/settings.json:

{
  "claudeAiMcpServers": {
    "enabled": ["Slack", "Sentry", "Sourcegraph"],
    "disabled": ["Figma", "Airtable", "Box"]
  }
}

Or alternatively, a simpler denylist approach:

{
  "disabledClaudeAiMcpServers": ["Figma", "Airtable", "Box", "Hex"]
}

Current Workaround

The only workaround is to disable all claude.ai MCPs with ENABLE_CLAUDEAI_MCP_SERVERS=false and then manually re-add desired servers via claude mcp add, which loses the managed auth benefits.

Context

This came up in internal discussion at Lyft where multiple engineers expressed wanting to keep some servers (like Slack) but hide the majority they don't use.

View original on GitHub ↗

4 Comments

shaneauerbach · 6 months ago

Related Issues

#39662 — Add disabled field to user-configured MCP servers (e.g., ones added via claude mcp add)
#42126 — Add defaultDisabled field for plugin-authored MCP servers to prevent auto-enable on install

How this issue is distinct: Both of those address MCP servers that users or plugin authors configure themselves. This issue is specifically about the built-in claude.ai MCP servers (Slack, Figma, Sentry, Airtable, PagerDuty, etc.) that are automatically pushed to Claude Code for logged-in users. Today the only control is the all-or-nothing ENABLE_CLAUDEAI_MCP_SERVERS env var — there's no way to keep some (e.g., Slack, Sourcegraph) while hiding others (e.g., Figma, Box, Hex) without disabling all of them and manually re-adding the ones you want.

aviadlevy · 5 months ago

I would like that a lot as well.

The use case is clear: Many of us want access to official connectors for routines and other 'cloud work' but when working with Claude Code locally, we prefer using CLIs and skills instead of MCP.

Please consider supporting this.

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.