Guides
Ten guides on what an email MCP server is, how to actually work an inbox with one, and what to check before you hand any of them your mail. Written while building the thing, against a mailbox with 26,930 messages in it.
Editorial
Most of what is written about connecting AI to email is written by people who have not connected AI to email. It shows in the details: guides that tell you to turn on IMAP in Gmail, an option Google removed in January 2025; guides that send you to Office 365 Exchange Online for permissions that live under Microsoft Graph; guides that quote Microsoft's documented 4 MB message ceiling, which did not hold when we pushed an 18,684,476-byte message through it and Graph answered 202.
We wrote these while building the server. Every figure in them was measured against a real mailbox rather than read off a specification, and where the measurement disagreed with the vendor's own documentation we say so and show the number. Where we do not know something, the guide says that too, which is the part most of these pages leave out.
That you have a mailbox and an AI client, and that nobody has explained how the two are supposed to meet. No programming is assumed anywhere. Two of the guides go into protocol detail because the questions they answer genuinely need it, and both open with the short version for anyone who does not.
Start here
What an MCP server is, what it can reach, and which kind you need. Start here if the words are new.
The protocol in plain terms, the twenty-eight tools a mail server exposes, and the difference between an AI that can describe your inbox and one that can work it.
It answers
One is a program your client launches, the other is a URL your client calls. The distinction decides your whole setup, and it is the thing most people get wrong first.
It answers
Working methods
Working methods for triage, replies, searching and filing. Written from a mailbox of 26,930 messages rather than from first principles.
Read-only first, decide in batches, act last. The method leans on one property of the engine: reading a message does not mark it read, so a triage pass you abandon halfway leaves no trace.
It answers
Draft first, send second. What to put in the brief, why the threading headers matter more than the prose, and the four kinds of reply actually worth handing over.
It answers
Search matches strings; you remember meaning. Closing that gap is the single most useful thing an AI does with a mailbox, and it needs a different approach from typing in the search box.
It answers
Finding an hour four people can make is the task most worth handing over, and the one most easily got wrong. What free/busy actually tells you, why unknown is not free, and which of these will email somebody. Needs a calendar connected.
It answers
Connecting a mailbox does not connect a diary. There are three ways to connect one and they behave differently: one is a tick box, one is a sign-in, and one is an address whose capabilities have to be measured rather than assumed.
It answers
What a move actually does to a message, why delete means Trash and not gone, how folder naming differs by host, and the categories worth keeping an AI away from entirely.
It answers
Before you connect
What an AI can and cannot do to a mailbox, what to ask any vendor before connecting one, and the provider traps that stop people in their tracks.
About 7 min
It depends on the connector, not on the AI. Eight questions worth putting to any vendor before you connect a mailbox, with our own answers to all eight, in full.
It answers
Google reports 2-Step Verification as on and still refuses. The cause is which second factor you have, not whether you have one, and Google now steers new accounts straight into the dead end.
It answers
Limits
The same rule the rest of this site follows. Saying what is missing is cheaper than letting somebody find out.
They are not API documentation. If you are building your own MCP server, the specification at modelcontextprotocol.io is the thing to read, not this.
They do not walk through the control panel screen by screen. Panel screenshots go stale faster than anything else on a website, and a wrong one costs more than an absent one.
They do not cover contacts or files, because this server does not reach them. Calendars they do cover, on any mailbox that has one connected: Microsoft 365 with calendar access approved, or any host at all by the address of its calendar server.
They are not a review of other MCP mail servers. We build one, so we are the wrong people to write that comparison and you should be suspicious of anyone who is not.
The free tier is 5 calls a day on any mailbox, with no card, which is enough to work through any of these against your own mail before deciding whether it is worth paying for.