Skip to main content

​
Operator MCP Server

The Operator MCP server lets any MCP compatible client talk to Operator over HTTP or SSE. The Operator MCP server supports two transport methods. HTTP is recommended for new setups. 
{
  "mcpServers": {
    "operator": {
      "url": "https://mcp.operator.io/mcp",
      "headers": {
        "Authorization": "Bearer ${OPERATOR_API_KEY}"
      }
    }
  }
}

​
SSE (legacy)

{
  "mcpServers": {
    "operator": {
      "url": "https://mcp.operator.io/sse",
      "headers": {
        "Authorization": "Bearer ${OPERATOR_API_KEY}"
      }
    }
  }
}

​
Use with Codex

Codex treats Operator as a streamable HTTP MCP server. Add an entry to ~/.codex/config.toml: 
[mcp_servers.operator]
url = "https://mcp.operator.io/mcp"
http_headers = { Authorization = "Bearer sk_your_operator_api_key_here" }
Codex will send this key as a Bearer token when it calls the Operator MCP server. See the Codex MCP docs for more options: https://developers.openai.com/codex/mcp/

​
Use with Claude Code

Claude Code can also connect to Operator as a remote HTTP MCP server. The generic way to add a remote HTTP server with a Bearer token is: 
claude mcp add --transport http operator https://mcp.operator.io/mcp \
  --header "Authorization: Bearer sk_your_operator_api_key_here"
For more details and configuration options, see the Claude Code MCP docs: https://code.claude.com/docs/en/mcp

​
Available tools

This MCP server exposes a single tool, operator_chat, which lets MCP clients send chat style tasks and questions to Operator using the same chat completions format as the main API.