Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Unable to disable Claude_in_Chrome and Claude_Preview despite correct configuration [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#54965•Fetched 2026-05-01 05:49:48
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
mail4earnshaw-aimail4earnshaw-ai
Participants
github-actions[bot]github-actions[bot]mail4earnshaw-aimail4earnshaw-ai
Timeline (top)
labeled ×3commented ×1renamed ×1

I'm unable to disable the built-in Claude_in_Chrome and Claude_Preview MCP servers, even with proper configuration in both settings files and a fresh restart of Claude Code.

Error Message

Error Messages/Logs

Root Cause

I'm unable to disable the built-in Claude_in_Chrome and Claude_Preview MCP servers, even with proper configuration in both settings files and a fresh restart of Claude Code.

Code Example

{
  "disabledMcpjsonServers": [
    "Claude_in_Chrome",
    "Claude_Preview"
  ]
}
~/.claude.json (project-level)
For each project in the projects section:

"disabledMcpServers": [
  "Claude_in_Chrome",
  "Claude_Preview"
]


### What Should Happen?

Expected Behavior
Claude_in_Chrome and Claude_Preview should NOT appear in the loaded MCP tools list.

Actual Behavior
Both Claude_in_Chrome and Claude_Preview continue to load and appear in the context window (consuming ~30k tokens), despite being listed in disabledMcpServers / disabledMcpjsonServers.

Related Issues
This appears related to:

#13311 - "Bug: disabledMcpServers setting not enforced at session startup"
#37284 - "Desktop: No way to prevent built-in MCP servers from being injected into Code tab sessions"
Additional Context
I've verified that the field names match the settings.json schema exactly. The configuration is syntactically correct and validated without errors. The issue persists across multiple restarts and new sessions.

### Error Messages/Logs
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Summary

I'm unable to disable the built-in Claude_in_Chrome and Claude_Preview MCP servers, even with proper configuration in both settings files and a fresh restart of Claude Code.

Environment

  • Claude Code Version: [Check: About Claude Code]
  • Operating System: macOS [your version, e.g., macOS 14.2]
  • Browser: Chrome (for Claude_in_Chrome reference)

Configuration Applied

~/.claude/settings.json

{
  "disabledMcpjsonServers": [
    "Claude_in_Chrome",
    "Claude_Preview"
  ]
}
~/.claude.json (project-level)
For each project in the projects section:

"disabledMcpServers": [
  "Claude_in_Chrome",
  "Claude_Preview"
]


### What Should Happen?

Expected Behavior
Claude_in_Chrome and Claude_Preview should NOT appear in the loaded MCP tools list.

Actual Behavior
Both Claude_in_Chrome and Claude_Preview continue to load and appear in the context window (consuming ~30k tokens), despite being listed in disabledMcpServers / disabledMcpjsonServers.

Related Issues
This appears related to:

#13311 - "Bug: disabledMcpServers setting not enforced at session startup"
#37284 - "Desktop: No way to prevent built-in MCP servers from being injected into Code tab sessions"
Additional Context
I've verified that the field names match the settings.json schema exactly. The configuration is syntactically correct and validated without errors. The issue persists across multiple restarts and new sessions.

### Error Messages/Logs

```shell

Steps to Reproduce

Steps to Reproduce Configure disabledMcpjsonServers in ~/.claude/settings.json Configure disabledMcpServers in ~/.claude.json projects section Restart Claude Code completely (force quit if necessary) Start a new session Run /context command to check loaded MCP tools

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue may be resolved by checking the configuration files for any typos or inconsistencies and ensuring that the disabledMcpjsonServers and disabledMcpServers settings are correctly applied.

Guidance

  • Verify that the disabledMcpjsonServers and disabledMcpServers settings are correctly formatted and match the expected schema in the ~/.claude/settings.json and ~/.claude.json files.
  • Check for any typos or inconsistencies in the configuration files, as the issue may be related to a simple configuration error.
  • Review the related issues (#13311 and #37284) to see if there are any known workarounds or fixes that may apply to this situation.
  • Try removing and re-adding the disabledMcpjsonServers and disabledMcpServers settings to ensure they are being applied correctly.

Notes

The issue may be related to a regression in the Claude Code version 2.1.123, as it was reported to have worked in a previous version. However, without more information about the last working version, it is difficult to determine the exact cause of the issue.

Recommendation

Apply workaround: Given the potential regression and the fact that the configuration appears to be correct, applying a workaround such as manually removing the unwanted MCP servers from the loaded tools list may be the best course of action until a fix is available.

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…
#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Unable to disable Claude_in_Chrome and Claude_Preview despite correct configuration [1 comments, 2 participants]