Codex MCP for email automation: connect Codex to Mimeo

What Codex can do in Mimeo

Build and change flows. Read the schema, save a draft flow, validate it, dry-run it on a real subscriber, and make it live only when you say so.
Write emails and segments. Draft an email, preview it as a real person, send yourself a test, and define segments as rules.
Answer questions from live data. Look people up, read their email activity and pull reports for any email, sequence, flow or broadcast.
Work on files you review. In the manager repo, ./bin/mimeo pull, edit, ./bin/mimeo diff, then ./bin/mimeo push, which validates and rehearses the change on your Mimeo before it applies.

The MCP docs list every tool.

Set up the manager repo: download the Mimeo Manager ZIP from your Mimeo account, create a token under Settings → Agents & API → Manager repo, and run ./bin/mimeo init --host https://mimeo.example.com with your own address. See your manager repo.
Put the token in your environment: export MIMEO_TOKEN="$(cat .mimeo/token)".
Add Mimeo's MCP server to Codex's ~/.codex/config.toml, or to the project's .codex/config.toml:

[mcp_servers.mimeo]
url = "https://your-mimeo.com/mcp"
bearer_token_env_var = "MIMEO_TOKEN"

Start Codex in the manager repo and check the server under /mcp. Ask it to read the repo's CLAUDE.md first: it holds the operating rules, such as rehearsing a flow before it goes live.

Questions

Does Codex read the manager repo's .mcp.json?

No. Codex keeps MCP servers in its own config.toml, so add Mimeo there once, as below.

Can Codex send email by mistake?

MCP needs a full-access token, and full access includes sending. Ask Codex to rehearse a flow and test-send before anything goes live; let an AI agent run your email without accidental sends shows the checks.

Does it work with other agents?

Yes. Any MCP client works, and Claude Code is wired up by the manager repo already.