Connect tools with MCP

🎯Goal. Extend Codex with external tools and data through the Model Context Protocol.

1. 1Codex supports MCP servers — add a STDIO or streaming-HTTP server in ~/.codex/config.toml, or manage them with the codex mcp CLI commands.
2. 2Codex launches configured servers automatically when a session starts, so the tools are ready without extra steps.
3. 3Use MCP to give Codex access to your own tooling or data sources beyond the local repo.

✓You'll see. Codex calling a connected MCP tool mid-task, using data or actions that live outside your codebase.

💳Cost. MCP adds capability, not a separate fee — you still pay only for model usage on your plan.

💡Takeaway. MCP plugs your own tools into Codex — configure a server once in config.toml and every session can use it.