Skip to content

MCP servers configuration not available in Settings UI #32220

Open

Description

@AnetteLarios

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.31428

What subscription do you have?

Codex LLM enterprise

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

There is no way to configurate or trigger authentication from the settings module in codex. The MCP servers configuration does not exist.

What steps can reproduce the bug?

  • Open codex
  • Go to settings
  • Look up MCP servers

Actual result

The results from the bar lookup says that the module should be in "General" configuration but it is not there.

What is the expected behavior?

MCP servers configuration displayed in UI of Settings module

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Jul 10, 2026
  2. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    mcpIssues related to the use of model context protocol (MCP) servers
    on Jul 10, 2026
  3. TyceHerrman commented on Sep 5, 2026

    @TyceHerrman

    also issue on macos

  4. alisterwayne8-web commented on Sep 21, 2026

    @alisterwayne8-web

    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:

    • Windows
    • Codex CLI 0.155.1
    • n8n 2.39.10 instance-level MCP (Streamable HTTP + OAuth)

    What worked:

    1. Add the MCP server from CLI:
    codex mcp add n8n --url "https://YOUR-N8N-HOST/mcp-server/http"
    1. In %USERPROFILE%\.codex\config.toml, use file-backed OAuth credentials:
    mcp_oauth_credentials_store = "file"

    For the n8n-generated Codex setup, this feature flag was also required in my case:

    [features]
    experimental_use_rmcp_client = true

    Server config:

    [mcp_servers.n8n]
    url = "https://YOUR-N8N-HOST/mcp-server/http"
    1. Re-authenticate:
    codex mcp logout n8n
    codex mcp login n8n
    1. Verify:
    codex mcp list

    This showed n8n -> enabled -> OAuth and created %USERPROFILE%\.codex\.credentials.json.

    1. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingmcpIssues related to the use of model context protocol (MCP) serverswindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions