MCP in Codex.
A TOML section or one CLI command.
Codex configures MCP servers in ~/.codex/config.toml, with a CLI to manage them so you rarely edit the file by hand. The same config drives the CLI and the IDE extension. Here's the setup for remote and local servers, with Amie's calendar-and-notes server as the example.
Add a server
For a remote server, the config is two lines. Add this section to ~/.codex/config.toml:
[mcp_servers.amie] url = "https://mcp.amie.so"
[mcp_servers.my-local-server] command = "npx" args = ["-y", "@some/mcp-server"]
codex mcp add amie --url https://mcp.amie.so
Restart Codex, and the first time a tool needs your account it'll open a browser window for the OAuth sign-in. Approve it once; Codex refreshes the token from then on. On older Codex builds, remote HTTP servers sat behind experimental_use_rmcp_client = true, so if the url field seems ignored, update Codex before debugging further.
Verify it's loaded
codex mcp list
What MCP tools do you have from the amie server? List my next three events.
If the server doesn't appear, it's almost always TOML: a typo in the [mcp_servers.amie] header or a missing quote makes Codex skip the section without an error. Validate the file and restart.
What you get with Amie connected
Codex can read your schedule across every Google and Outlook account you've connected to Amie, book meetings and send invites, RSVP, manage todos, and search meeting notes and transcripts. It's one server instead of a self-hosted Google Calendar MCP container plus a todo server plus a notes server, and there's no Google Cloud setup at all.