You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MCP servers configuration not available in Settings UI #32220
Confirmed on Windows: I hit the same missing Settings → MCP Servers UI, but was able to get a remote OAuth MCP working in Codex Desktop through the CLI/config path.
This showed n8n -> enabled -> OAuth and created %USERPROFILE%\.codex\.credentials.json.
Fully quit Codex Desktop, relaunch it, and start a new thread. After that, Desktop was able to call the n8n MCP tools and list workflows successfully.
So the missing Settings UI did not block MCP usage, but the CLI/config route was required. This also appears related to the Windows OAuth persistence issue in #28201.
Security note: mcp_oauth_credentials_store = "file" stores OAuth credentials in .codex\.credentials.json, readable by the same user context. This is a workaround, not the ideal long-term fix.
Activity
TyceHerrman commentedon Sep 5, 2026
also issue on macos
alisterwayne8-web commentedon Sep 21, 2026
Confirmed on Windows: I hit the same missing Settings → MCP Servers UI, but was able to get a remote OAuth MCP working in Codex Desktop through the CLI/config path.
Tested setup:
0.155.12.39.10instance-level MCP (Streamable HTTP + OAuth)What worked:
codex mcp add n8n --url "https://YOUR-N8N-HOST/mcp-server/http"%USERPROFILE%\.codex\config.toml, use file-backed OAuth credentials:For the n8n-generated Codex setup, this feature flag was also required in my case:
Server config:
This showed
n8n -> enabled -> OAuthand created%USERPROFILE%\.codex\.credentials.json.So the missing Settings UI did not block MCP usage, but the CLI/config route was required. This also appears related to the Windows OAuth persistence issue in #28201.
Security note:
mcp_oauth_credentials_store = "file"stores OAuth credentials in.codex\.credentials.json, readable by the same user context. This is a workaround, not the ideal long-term fix.