Codex MCP Servers: Config, Transports, and What Works
MCP servers worth wiring into OpenAI Codex, by category — plus config.toml syntax, codex mcp add, stdio vs streamable HTTP, and what Codex drops.
20 posts
MCP servers worth wiring into OpenAI Codex, by category — plus config.toml syntax, codex mcp add, stdio vs streamable HTTP, and what Codex drops.
Codex has no native Bitbucket support, but Atlassian's Rovo MCP server now covers Bitbucket Cloud. Here's how to wire it up and where it stops.
Yes, CircleCI's official MCP server works with Codex — build logs, flaky tests, pipeline reruns in-session. But nobody's watching CI when you log off.
Yes, Codex connects to Cloudflare's official remote MCP servers — Workers, DNS, the full API — but it works in sessions, not as an always-on ops layer.
Yes, OpenAI Codex can connect to Datadog through Datadog's official MCP server — great for debugging sessions, but it won't watch your monitors overnight.
Codex has no native GitLab integration — but GitLab's official MCP server connects it in minutes. What works, what doesn't, and where the gaps are.
Yes, Grafana's official MCP server connects to Codex — dashboards, Prometheus, Loki, alert rules in-session. The overnight watching is a different tool.
Yes, Postman's official MCP server lists Codex as a supported client: collections, specs, and environments in your session. Monitoring is another story.
Sentry ships an official MCP server that plugs straight into Codex — real stack traces in your debugging sessions. But Codex won't watch Sentry for you.
Supabase's official MCP server gives Codex 20+ tools — queries, migrations, Edge Functions, branches. Here's the setup and where the automation stops.
Vercel's official MCP server lists Codex CLI as a supported client — deployments, logs, and docs in your sessions. But Codex won't watch your deploys.
Yes, OpenAI Codex integrates natively with GitHub — cloud tasks, @codex on PRs, and code review — but it's a developer tool, not a no-code ops assistant.
You can connect Jira to OpenAI Codex via the Atlassian MCP server so it reads tickets as context — but it's a developer config, not a no-code Jira assistant.
You can connect Linear to OpenAI Codex via its MCP server so it reads issues as context — but it's a developer config, not a no-code Linear assistant.
You can connect Notion to OpenAI Codex via an MCP server so it pulls docs as context — but it's a developer config, not a no-code Notion assistant.
You can wire OpenAI Codex to Google Calendar through an MCP server, but it's a developer setup and Codex is a coding agent, not a scheduler.
Yes, Codex connects to Gmail. The first-party plugin holds one Google account; connect every Gmail and Outlook mailbox to Carly and reach them in one session.
Codex has a first-party Outlook Calendar plugin that books and reschedules. Where free/busy runs out, and how Carly closes the loop on its own.
Codex has a first-party Outlook Email plugin. What it sends, the plain-text limit, and how one MCP server puts every Outlook and Gmail mailbox in reach.
Codex reaches Slack two ways: an app that launches coding tasks and a plugin that summarizes channels. Neither one runs Slack for you.