[FEATURE] Disable claude.ai-integrated MCPs per surface (Claude Code vs Chat/Cowork)

Resolved 💬 3 comments Opened Apr 14, 2026 by marwanfahmi Closed May 23, 2026

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

When claude.ai integrations (Gmail, Google Calendar, Slack, etc.) are connected at the account level, they are automatically injected into every Claude Code session consuming tokens on every request even when not used. There's currently no way to disable these MCPs specifically for Claude Code while keeping them active in Chat or Cowork.

Proposed Solution

Add a per-surface MCP toggle, either in claude.ai account settings or via a Claude Code settings.json field (e.g. disabledCloudMcpServers) so users can opt out of account-level MCP injection in Claude Code sessions.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

Every Claude Code session pays the token cost of injecting unused MCP tool definitions, which adds up significantly for heavy CLI users.

View original on GitHub ↗

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