Email for Codex

Connect Codex to your email

1. 1. Install Fluxmail and connect a mailbox

   Install the CLI, create the first administrator, and connect Gmail with the local OAuth flow. Outlook needs a Microsoft app registration; IMAP needs provider credentials. The quickstart covers Docker and provider setup.

   npm install -g fluxmail
   fluxmail setup --name "Your name" --email you@example.com
   fluxmail accounts add gmail

   • Gmail and Workspace OAuth
   • Outlook and Exchange setup
   • IMAP and SMTP credentials

2. 2. Add Fluxmail to Codex

   For Codex CLI on the same computer as Fluxmail, add the stdio server:

   codex mcp add fluxmail -- fluxmail stdio --profile read-only

3. Or connect over HTTP

   To connect over Streamable HTTP, create an API key with fluxmail apikey create --name codex --profile read-only. Start the server with fluxmail serve unless Docker is already running it, then add it to ~/.codex/config.toml:

   [mcp_servers.fluxmail]
   url = "http://localhost:8977/mcp"
   http_headers = { Authorization = "Bearer fmk_..." }

Bring a customer thread into a coding task

The setup above uses read-only access. Try this prompt with a mailbox you connected:

Find an email thread about [replace with a subject you know exists]. Read it and list the reported problem, expected behavior, and unanswered questions. Include the sender and subject so I can verify the source. Do not change my mail.

Check the result

The summary should match the thread in Gmail or Outlook. Check that Codex distinguishes what the sender reported from its own suggested fix. Searching an unfamiliar subject may correctly return no results.

To create drafts, change the stdio profile or HTTP key to read-write and reconnect. That profile also allows organizing and trashing mail, but cannot send or permanently delete messages. Review a draft in your mail client before sending it yourself.

If the connection does not work

• Run codex mcp list in the CLI, or check the server in the app MCP settings. Start a new session after changing the configuration.
• If the server connects but no mailbox appears, run fluxmail accounts list as the same operating-system user. Check the instance, member, and mailbox scope used by the client.
• For a command-not-found error, use the absolute path to the installed Fluxmail executable. For HTTP 401, check the API key and Authorization header. For a permission error, check the key or stdio profile before retrying.