This page covers configuring MCP servers for Codex threads launched through Jaidu.

​
Overview

MCP servers extend Codex with additional tools and resources. You can use them to add browser automation, documentation lookups, remote logs, issue-management tools, and other capabilities to your Codex threads.

​
Accessing MCP Server Configuration

  1. Navigate to Settings in the Workspaces navbar
  2. Click the MCP Servers tab
  3. Edit the Codex MCP configuration JSON
MCP Server configuration page showing the Codex JSON configuration editor and popular servers
Jaidu provides one-click installation for popular MCP servers. Click a card to insert a pre-configured MCP server into the Codex configuration.
Popular MCP servers including Context7, Playwright, Exa, Chrome DevTools, and Dev Manager

​
Adding Custom MCP Servers

You can also add your own MCP servers manually:
1

Open the Codex Configuration

Open Settings → MCP Servers and review the existing Codex JSON.
2

Update the JSON

Add your custom MCP server alongside any existing entries.
{
  "mcpServers": {
    "existing_server": {
      "command": "npx",
      "args": ["-y", "some-existing-server"]
    },
    "my_custom_server": {
      "command": "node",
      "args": ["/path/to/my-server.js"]
    }
  }
}
3

Save and Test

  1. Click Save Settings
  2. Start or continue a Codex thread
  3. Check Codex logs if a server does not connect
These changes persist in your Codex configuration and remain available across threads.

​
Best Practices

Add only the MCP servers you expect to use regularly. Too many tools dilute the agent’s context and make tool selection noisier.
Prefer servers that directly support your workflow, such as browser automation for frontend work or documentation retrieval for framework-heavy tasks.