Set up MCP servers

Add MCP servers for Claude Code, Codex, and Cursor Composer workflows so agents can use shared tools and context

Use MCP servers when every Conductor workspace should give agents the same external tool access: docs search, issue tracking, databases, dashboards, or internal APIs.

This guide sets up a stdio MCP server for Claude Code, Codex, and Cursor Composer workflows. For exact config fields, transports, scopes, and security notes, see the MCP reference.

Before you start

You need:

A repository already added to Conductor.
A local Conductor workspace.
Claude Code, Codex, or Cursor Composer selected for the workflow you want to use.
Any required credentials for the MCP server.

MCP servers are loaded by the agent host. If you change Claude Code or Codex MCP configuration after a Conductor session has started, refresh MCP status and start a new session when you need the new tools in the model context.

Cursor Composer MCP servers are configured in Cursor. Use that path when you open a Conductor workspace in Cursor and want Cursor Composer to use project-level or user-level MCP servers.

Add an MCP server

Choose the scope

Use user scope for personal tools you want everywhere. Use project scope for tools that should follow one repository.

Scope	Use it for	Claude Code path or command	Codex path or command	Cursor Composer path
User	Personal docs search, personal issue tracker auth	`claude mcp add -s user ...`	`codex mcp add ...`	`~/.cursor/mcp.json` or Cursor MCP settings
Project	Repository-local MCP config shared with teammates	`.mcp.json` in the repository root	`.codex/config.toml` for that project	`.cursor/mcp.json` in the repository root

If the server needs secrets, keep credentials out of committed files. Use environment variables or personal config for tokens.

Add the server for Claude Code

Run the Claude Code MCP command from a terminal:

claude mcp add context7 -s user -- npx -y @upstash/context7-mcp

The -- separates Claude Code options from the command that starts the MCP server.

For project-level Claude Code config, add .mcp.json at the repository root:

.mcp.json

{
    "mcpServers": {
        "context7": {
            "command": "npx",
            "args": ["-y", "@upstash/context7-mcp"]
        }
    }
}

Add the server for Codex

Run the Codex MCP command from a terminal:

codex mcp add context7 -- npx -y @upstash/context7-mcp

Codex writes the server to ~/.codex/config.toml. You can also edit that file directly:

~/.codex/config.toml

[mcp_servers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp"]

For Streamable HTTP servers, use the server URL instead of a local command:

codex mcp add openaiDeveloperDocs --url https://developers.openai.com/mcp

Add the server for Cursor Composer

Open the Conductor workspace in Cursor with Open In or Command O.

For project-level Cursor Composer config, add .cursor/mcp.json at the repository root:

.cursor/mcp.json

{
    "mcpServers": {
        "context7": {
            "command": "npx",
            "args": ["-y", "@upstash/context7-mcp"]
        }
    }
}

Cursor also supports user-level MCP configuration in ~/.cursor/mcp.json and through Cursor's MCP settings UI. Use user-level config for personal tools; use project-level config when everyone opening the repository in Cursor should get the same MCP server definition.

Check status in Conductor

Open the Conductor workspace and select the session that should use the MCP server.

If the MCP status indicator is enabled, click the plug icon in the composer and use the refresh button. You can also run /mcp-status in the composer to open the status dialog.

Conductor shows the Claude Code or Codex servers it can discover for the selected agent. If a server needs OAuth, use the authentication action from the status row.

For Cursor Composer, check server status in Cursor's MCP UI. Conductor-hosted Cursor sessions do not currently surface Cursor MCP server status in Conductor's MCP status UI.

Ask the agent to use the tool

Start a new message that names the server's purpose. For example:

Use Context7 to look up the latest React Query docs, then update this hook.

When the agent calls an MCP tool, Conductor renders the tool call in the session transcript. Approval prompts may appear depending on your agent settings and the server's tools.

For shared repository behavior, prefer committed project config and personal credentials:

Commit .mcp.json only when the listed servers are safe and useful for everyone using Claude Code in the repository.
Commit .cursor/mcp.json only when the listed servers are safe and useful for everyone opening the repository in Cursor.
Keep tokens in environment variables, user config, or secret managers.
Document required tokens in your project README or setup docs.
Use Conductor environment variables when a local workspace needs provider or tool credentials available to agent processes.

If your team is migrating from Cursor MCP config to Claude Code in Conductor, copy project MCP servers from .cursor/mcp.json to .mcp.json. See Migrate MCP servers from Cursor.

Troubleshooting

Next steps

Use MCP for transports, scopes, config examples, and security notes.
Use Cursor for Conductor's Cursor Composer session behavior.
Use Security and permissions to understand how agent tools and approvals work.
Use Work with Cursor and VS Code if you are moving MCP servers from Cursor.

The server does not appear in Conductor

The server starts locally but fails in another workspace

On this page