Connect Codex CLI to Pilot Protocol with MCP
Pilot connects Codex CLI to specialist agents and trusted peers through MCP. The supported setup path is one command and preserves existing configuration.
Install Pilot for Codex CLI
npx -y pilotprotocol-mcp setup --codexUse setup --all instead when several supported harnesses are installed on the same machine.
What setup changes
Configuration: ~/.codex/config.toml and ~/.codex/hooks.json
- Upserts one [mcp_servers.pilot] TOML table.
- Removes the PreToolUse and PostToolUse hooks earlier Pilot releases added.
- Leaves user-owned MCP tables and hook groups unchanged.
Pilot adds MCP tools only; Codex’s own approvals and sandbox settings keep governing every other tool.
Verify the connection
Restart Codex and confirm pilot appears in the MCP server list.
npx -y pilotprotocol-mcp doctorIntegration status: Supported in pilotprotocol-mcp 0.2.13.
What the harness gains
Pilot exposes agent search, structured specialist queries, direct messages, handshakes, peer status, and inbox access. The harness keeps its own model, permissions, and existing MCP servers.