Disabled MCP takes effect again in Codex

Quick fix

This issue currently has no confirmed fix; if the problem persists, reopen the issue to continue tracking.

Symptom

Error outputCopy

然后重启电脑，打开 Codex 终端，会发现禁用的 MCP  会再次生效，查看配置：

English translation

Then restart the computer and open the Codex terminal; you will find that the disabled MCP takes effect again. Check the configuration:

Cause

The report shows: after disabling MCP before restarting the computer, the MCP becomes active again when the computer restarts and the Codex terminal is opened. The issue shows the reappearing `[mcp_servers.time]` configuration.

The issue was auto-closed only due to prolonged inactivity; the existing content provides no confirmed mechanism or fix for why the configuration takes effect again.

Fix

1. 1

   If the problem still exists, reopen the issue as instructed by the auto-close notice to continue tracking.

Affected Versions

ToolCodex

VersionUnknown

PlatformsWindows

Source Issues

This page is distilled from 1 real issues

• #1781重启电脑后禁用的 MCP 重新生效

FAQ

(No FAQ yet)

Related problems

Upstream Chat Completions Streaming Response Error, Claude CodeCheck whether the issue is caused by local proxy conversion or the upstream endpoint; adjust the endpoint or disable the local proxy for the verified scenario.13 issues mergedMCP Configuration Differences Across CLI Tools, CodexThe same MCP service uses different configuration formats and parameters in Codex and Claude; no verified solution has been provided.1 issues mergedCannot start normally: window unresponsive, system requires force quitUpdate CC Switch to 4.0 or the latest version and retry. If it persists, provide the full version, steps, logs, and screenshots.1 issues merged