claude-code - 💡(How to fix) Fix [FEATURE] Disable claude.ai-integrated MCPs per surface (Claude Code vs Chat/Cowork) [1 comments, 2 participants]

TL;DR

Implement a per-surface MCP toggle to allow users to opt out of account-level MCP injection in Claude Code sessions.

Guidance

• Investigate adding a disabledCloudMcpServers field to the Claude Code settings.json file to enable users to disable specific MCPs.
• Consider implementing a toggle in the claude.ai account settings to provide an alternative way for users to manage MCP injection.
• Evaluate the token cost implications of injecting unused MCP tool definitions in Claude Code sessions to determine the potential benefits of the proposed solution.
• Assess the feasibility of implementing a per-surface MCP toggle, considering the technical requirements and potential impact on existing integrations.

Example

No code snippet is provided as the issue does not contain sufficient technical details to support a specific implementation.

Notes

The proposed solution may require significant changes to the existing architecture, and careful consideration should be given to the potential impact on users and the overall system.

Recommendation

Apply workaround: Implement a per-surface MCP toggle to allow users to opt out of account-level MCP injection in Claude Code sessions, as this will provide a targeted solution to the problem and help reduce the token cost for heavy CLI users.