Guides
14 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's written about connecting AI to email is written by people who haven't connected AI to email. It shows in the details. There are guides that:
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 don't 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 2 are supposed to meet. No programming is assumed anywhere. 2 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.
Claude has 4 ways into a mailbox and they do different things. Which one reads, which one sends, which one files, which plan each needs, and the one route that reaches an Outlook.com or IMAP mailbox.
It answers
ChatGPT reads Gmail and Outlook once they are connected, and has sent email since June 2026. What OpenAI documents it doing to your own mailbox, what it leaves unstated, and the MCP route that covers the rest.
It answers
The protocol in plain terms, the 37 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 4 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 4 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 3 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
A clean-up we recorded in Claude: what it deleted, archived and filed, the 7 calls it took, what it left alone on purpose and what it got wrong. Plus what Claude's own Gmail connector does when you ask it to delete.
It answers
Claude's own Gmail connector holds one Google account. How to run every mailbox you have side by side in Claude, named so it picks the right one, what that costs, and what ChatGPT does with several.
It answers
Give a colleague or an assistant their own connection to a mailbox you own, at a level and under a cap you set, without handing over a password. Then the part nobody else writes down: how a claim on a message actually works, and where a mail server can refuse it.
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 8 min
It depends on the connector, not on the AI. 8 questions worth putting to any vendor before you connect a mailbox, with our own answers to all 8, 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 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, a Google calendar signed in to, or any host at all by the address of its calendar server.
An address book comes with the sign-in on Microsoft 365. Everywhere else, on a mailbox that uses a password, it is the same kind of step: its Google contacts by a Google sign-in, set up on the Gmail page, or any other book by the address of a CardDAV contacts server.
The set-up page for that route is the CalDAV and CardDAV page rather than a guide.
They are not a review of other MCP mail servers. We build one, so read any comparison from us with that in mind: ours quotes each competitor from its own page, with the date it was read, so you can check it.
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.