Codex
Paste a short TOML block into `~/.codex/config.toml`, restart Codex, done.
What are the connection details?
| Server URL | https://mcp.unitpost.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Auth header | Authorization: Bearer pk_live_YOUR_KEY(production key from www.unitpost.com) |
| Tools | one per API operation (emails_send, campaigns_send, …) |
How do I connect Codex?
Create a production API key
Open https://www.unitpost.com → Settings → API keys → create a scoped key. Copy the full
pk_live_…value (shown once). In every snippet below, replacepk_live_YOUR_KEYwith that value.Must be production. Keys from unitpost.dev only work on the dev API. This MCP URL is production (
mcp.unitpost.com) — a .dev key returns 401 Invalid API key on tool calls even if the server appears connected.Open the Codex config
Edit `~/.codex/config.toml` (create the file if it does not exist).
Paste this TOML
Replace
pk_live_YOUR_KEY— keepBearerinside the quotes.TOML[mcp_servers.unitpost] url = "https://mcp.unitpost.com/mcp" [mcp_servers.unitpost.http_headers] Authorization = "Bearer pk_live_YOUR_KEY"Grant only the scopes the agent needs (e.g.
emails:sendforemails_send). Prefer a revocable key dedicated to the agent.Restart and verify
Restart Codex so it reloads the config. unitpost tools should be available to the agent.
Send a test
Ask Codex to send an email from a verified domain and confirm it in Unitpost Activity.