Skip to content
CC Switch WikiUnofficial Community Wiki

A disabled MCP becomes active again after restarting the machine - Codex

Quick fix

No official fix yet: clean the conflicting MCP nodes out of the config file by hand, and use deeplink import carefully so custom settings survive.

Symptom

Section titled “Symptom”
Error output
重启电脑，打开 Codex 终端，会发现禁用的 MCP  会再次生效
English translation

Restart the machine and open the Codex terminal, and you find the disabled MCP active again

Cause

Section titled “Cause”

cc-switch rebuilds and overwrites templates when managing Codex config. On a system restart, or when importing a provider through a deeplink, the underlying `build_codex_settings` regenerates a fixed TOML template, so a disabled MCP service (`[mcp_servers.time]`, for example) is written back and becomes active again, while non-provider custom settings such as `web_search` are discarded. Separately, Codex uses TOML while Claude uses JSON, so managing the same MCP service under different CLIs readily creates config conflicts. Since no fix has been merged for the related issues (some closed as stale), manual intervention is the only option today.

Fix

Section titled “Fix”

  1. With no automatic fix available officially, open the Codex config file by hand and delete or comment out the MCP nodes that came back (`[mcp_servers.time]` or `[mcp_servers.serena]`, for example).

  2. When importing a provider deeplink, avoid links carrying an inline `config` payload, so `build_codex_settings` does not rebuild the template and overwrite your custom fields.

Affected Versions

Section titled “Affected Versions”
ToolCodex
VersionUnknown
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 3 real issues

FAQ

Section titled “FAQ”
Why does configuring the same MCP service in Codex and Claude create a conflict?
Because the config formats of the two CLIs differ — Codex uses TOML while Claude uses JSON — so managing them together can overwrite or conflict.
Why did my `web_search` and other custom config disappear after importing a deeplink?
After you confirm the import, `build_codex_settings` rebuilds a fixed TOML template, and that process discards non-provider Codex custom settings.
Section titled “Related problems”
claude mcp list shows ✘ Failed to connectOn Windows cc-switch wraps the MCP npx command in cmd /c, breaking the stdio pipe. Edit ~/.claude.json back by hand, or rewrite with claude mcp add.10 issues mergedcc-switch loses Claude Code / Codex MCP configurationUpgrade cc-switch, disable or use unified MCP takeover carefully, find the one broken MCP entry, and fix rewritten command/type/path fields.14 issues mergedEvery click first pops up the system folder picker - cc-switchEdit src/App.tsx to remove the pickDirectory() call in handleOpenTerminal, so opening a terminal stops forcing a folder picker.3 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.