Send email from Codex
The Codex CLI, IDE extension and app share one config file, so connecting once covers all three. Add the server URL and sign in with OAuth in the browser.
Add the server
Run the command below; Codex detects OAuth and starts sign-in right away. No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically. In the Codex app or IDE extension instead: Settings → MCP servers → Add server, name it
unitpost, choose Streamable HTTP, paste the server URL and save, then click Authenticate.Shellcodex mcp add unitpost --url https://mcp.unitpost.com/mcpLeave the bearer token and header fields empty: OAuth needs neither.
Sign in again when needed
If sign-in was skipped or has lapsed, run
codex mcp login unitpost, or click Authenticate next to unitpost in the app's MCP servers list.Verify
Run
codex mcp list. unitpost showsOAuthin the Auth column (Not logged inmeans sign-in is still pending). In a session,/mcplists its tools, likeemail_sendandemail_domains_list.Don't see it? Fully quit and reopen the client — closing the window is often not enough — then check again.
Send a test
Ask Codex to send an email from a verified domain and confirm it in Unitpost Emails.
No browser on this machine? For headless setups, CI, SSH, or clients that can only paste a key, use the API-key setup instead.