MCP setup guide

Codex

Codex stores MCP servers in a TOML config and keeps tool approval as a separate decision. That makes it a good choice when you want a hosted server available but still want a confirmation step before a write.

Paths checked against the client's docs · November 2026

Surfaces

CLI · IDE extension

Scope

Project or global

Project config.codex/config.toml
Installer agentcodex
1 / How it works

How Codex handles MCP

Codex stores MCP servers in a TOML config and keeps tool approval as a separate decision. That makes it a good choice when you want a hosted server available but still want a confirmation step before a write.

Project or global. Project scope keeps the server with the repository; global scope makes it available in every workspace.

Best for

Terminal-first work with a clear approval boundary.

Installer flag-a codex
2 / Where it goes

Where the MCP config lives

The installer writes this file for you. Use the paths below when you want to inspect, edit, or remove a server by hand.

Project
.codex/config.toml
Global
~/.codex/config.toml

Project paths are relative to the workspace. Global paths are per user. On Windows, ~ means your user folder; use %USERPROFILE% in Explorer or PowerShell. A project config is shared with the team; a global config is personal.

3 / Install

Add a remote server

Start with a server in the MCP directory, or use your provider's endpoint. The examples use https://mcp.example.com/mcp so you can see the shape; replace it with the real URL.

  1. 01

    Find the endpoint

    Open a server page and copy its hosted endpoint. Do not use a local command or an npm package name for a remote server; those are different connection types.

    Open the MCP directory
  2. 02

    Run the installer

    Use the project config for a repository-specific server, or the global config for every workspace. The server name becomes example in the config.

    Codex · project
    # Add this to Codex MCP settings:
    [mcp_servers."example"]
    url = "https://mcp.example.com/mcp"
    
    Codex · global
    # Add this to Codex MCP settings:
    [mcp_servers."example"]
    url = "https://mcp.example.com/mcp"
    

    Codex supports stdio and Streamable HTTP servers; legacy SSE is not a Codex transport. Use an HTTP endpoint or a local bridge if the server is SSE-only.

  3. 03

    Authorize if the provider asks

    The first connection may open a browser for OAuth. Sign in with the provider and approve only the scopes you need. If the server uses an API key, create it in the provider's dashboard and add it through the client's auth flow or config.

    Never paste a provider token into a project config you will commit. Prefer the client's secret store or a user-level config for credentials.

  4. 04

    Reload and verify

    Start a new Codex session and ask it to list its MCP tools, or run `codex mcp list`.

    Then ask for a task, not a tool: “Find the open issues assigned to me” or “Summarize the latest release.” The client decides which advertised tool to call.

4 / Use

What changes in the chat

Once the server is connected, its tools appear in the client's tool list. You still talk to the agent normally; MCP is plumbing, not a different chat interface.

Read

“Find the customer notes mentioning the migration and summarize the blockers.”

Write

“Create a draft page with this outline, but do not publish it yet.”

Investigate

“Check the failed deployment and list the last three changes that touched it.”

Verify

“Which MCP tools do you have available for this task?”

If the agent ignores the server, check that the server is enabled and that its tools are approved. Some clients require a per-tool confirmation before the first call.

5 / Troubleshooting

When it does not connect

The server is missing

Confirm the file exists at the path above, the JSON or TOML is valid, and you restarted the client or opened a new session.

It connects but tools are empty

Enable the server in the client's MCP UI, approve its tools, and check that the provider has not revoked your token.

OAuth keeps reopening

Remove the server from the client, revoke the app's access in the provider's account settings, then add it again.

A project server is ignored

Some clients require you to trust the folder before loading project MCP config. Trust the repository, then start a new session.

6 / Notes

What to watch for in Codex

  • Codex reads `config.toml`, not JSON. The installer writes the correct TOML shape.
  • Set `default_tools_approval_mode` on the server to `auto`, `prompt`, `writes`, or `approve`. Use `writes` to prompt only for tools that are not read-only.
  • Start a new Codex session after changing the config so the tool list is reloaded.
7 / Remove

Remove or reset the server

Remove the server when it is no longer needed, or reset it when a credential or connection state gets stuck.

  1. Remove the server table from .codex/config.toml or ~/.codex/config.toml.
  2. Start a new Codex session so the TOML config is reloaded.
  3. Check that the server no longer appears in the MCP tool list.

Remove and re-add the server, then review the approval policy before the first tool call.

Sources

Official documentation

Client behavior changes. These links are the source of truth for paths, flags, and approval behavior.

Next setup guideCursor