Most people who talk to ChatGPT every day have never heard of MCP, and they shouldn't have to. Until this week, giving ChatGPT an OpenMail inbox meant switching on Developer mode, creating an app by hand, pasting a server URL, and ticking a box that says you understand the risks. I wrote that guide myself. It was four screenshots long, it only worked on paid plans, and I'm fairly sure most people closed the tab around screenshot two.
That path is gone. OpenMail is now listed in the ChatGPT plugin directory. You open the listing, click Install plugin, sign in to OpenMail once, and ChatGPT has an email address. That's the whole setup.
Why ChatGPT needs an inbox at all
The internet still runs on email. Signups, verification codes, invoices, the reply from the accountant, the quote from the supplier. ChatGPT can browse and reason about all of it, but without an address it is a visitor at every one of those doors. It can draft the email for you to send. It can't receive the answer.
The obvious fix is to connect your Gmail. I've written about why that goes wrong: Google treats agent behaviour as abuse, and a ban takes your Calendar, Drive and Photos with it. Beyond the ban risk, there's a quieter problem. Connecting your personal inbox gives the model every email you've ever received. Medical results, bank statements, the thread with your lawyer. That is a lot to hand over so an agent can read one verification code.
An agent needs its own address for the same reason an employee gets their own, not a copy of yours. Separate identity, separate permissions, and when it's done, you close it.
What the listing changes
Technically, nothing. It is the same MCP server at mcp.openmail.sh that Claude and Cursor have been using for months. What changed is who can reach it.
Developer mode was a Plus-and-above feature, so the free tier, the largest group of ChatGPT users, was locked out entirely. The directory is open on every plan. In a Business, Enterprise or Edu workspace an admin can allow it once for everyone instead of each person repeating the setup.
It also means OpenAI reviewed the server: what each tool does, how OAuth works, what we record. I won't pretend that review is a security audit, but it is a bar, and most MCP servers you can paste into Developer mode haven't cleared it.
One more thing I didn't expect: ChatGPT and Codex share the directory. Run /plugins in Codex CLI and the same inbox is there, with the same sign-in.
Setting it up
- Open the OpenMail listing and click Install plugin. Or open Plugins in ChatGPT and search for OpenMail.
- Click Connect OpenMail. The OpenMail console opens. Sign in, pick an organisation, and untick anything ChatGPT shouldn't have. Read is always on; Send, Setup and Domains are yours to withhold. Click Allow.
- Start a new chat and ask: “Set up an inbox for this agent and show me the address.”
The first time I did this it took under a minute, most of it on the consent screen deciding whether to grant Send. I did. ChatGPT asks before every send anyway, so the scope is a ceiling, not an autopilot.
What it's good at, and what it isn't
Good: anything that starts with “wait for the email”. Sign up for a service and finish the verification yourself. Read the invoice PDF in the latest thread and pull out the total. Triage what came in overnight and draft replies for the ones from people. Spam, bounces and no-reply mail are filtered before the model sees them, so it answers humans, not newsletters.
Not good: anything in your own mailbox. ChatGPT does not get Gmail or Outlook through this, by design. If what you want is “summarise my inbox”, this isn't the tool. If what you want is “give the agent an address and let it handle the correspondence”, it is.
Every permission can be revoked from MCP settings, and revoking cuts access immediately. The full reference, including Claude, Cursor and other clients, is at docs.openmail.sh/integrations/mcp.
If you try it and something is confusing, tell me. We have a tool for that too: ask ChatGPT to send OpenMail feedback and it lands on my desk.
Frequently asked questions
Does OpenMail work on the free ChatGPT plan?
Yes. The plugin directory is available on every ChatGPT plan. In a Business, Enterprise, or Edu workspace an admin may need to allow the plugin first.
Does ChatGPT get access to my personal email?
No. OpenMail gives ChatGPT its own inbox on an OpenMail address or your own domain. It never touches Gmail or Outlook. You pick which permissions it gets at sign-in and can revoke them any time from the console.
Can ChatGPT send email without asking?
Not by default. ChatGPT confirms before any write action, such as sending or replying. If you only want reading, untick Send when you connect.
Does the same plugin work in Codex?
Yes. ChatGPT and Codex share one plugin directory. Run /plugins in Codex CLI, or open Sources → Use plugins in the desktop app.
