What Is an IMAP MCP Server?

An IMAP MCP server is a service that lets an AI like Claude read and act on your real email inbox by combining two technologies: IMAP (the standard protocol for accessing email) and MCP (the Model Context Protocol, which defines how AI assistants connect to external tools). In plain terms, it is the bridge that lets Claude search your inbox, surface relevant threads, and help you take action on your email — all from a conversation.

If you have used Connect My Email (CME) to connect an inbox to Claude, you have already used an IMAP MCP server. CME handles the hosting, authentication, and tool definitions so you do not need to think about the protocol layer.

#Who This Is For

This explainer is for two audiences.

Non-technical users who have heard the term "MCP server" and want to understand what they are actually connecting when they link their inbox to Claude. The short answer: you are giving Claude a set of tools (read email, search email, take action on email) that work against your real inbox — not a demo dataset, not a sandbox.

Developers who are evaluating how to expose email functionality to an AI agent and want to understand the architecture: what IMAP does, how MCP wraps it, and where app passwords or OAuth tokens fit in.

#What IMAP Does

IMAP stands for Internet Message Access Protocol. It is the standard protocol that email clients — Outlook, Apple Mail, Thunderbird, and most others — use to retrieve and manage messages on a mail server. When you open your inbox in an email app, IMAP is what fetches the messages from the server and keeps them in sync.

IMAP operates over an authenticated TCP connection, typically on port 993 with TLS. Your client sends commands (fetch messages, search by subject, move to folder, delete), and the server responds. The messages stay on the server; the client is a view into them.

Every major email provider supports IMAP: Gmail, Outlook, Yahoo, iCloud, Zoho, Fastmail, AOL, ProtonMail (via a bridge), and any standard IMAP-capable server.

#What MCP Does

The Model Context Protocol is an open standard that defines how AI assistants connect to external data sources and tools. An MCP server exposes a set of named tools — functions with defined inputs and outputs — that a compatible AI client (like Claude) can call during a conversation.

When you install an MCP connector in Claude and give it a URL, you are telling Claude: "this server has tools you can use." Claude sees the tool names and descriptions, decides when to invoke them based on the conversation, and sends structured requests. The MCP server executes the request (reads your inbox, runs a search, flags a message) and returns the result.

For email, a well-designed MCP server exposes tools like:

• read_inbox — fetch recent messages with metadata
• search_email — search across subject, sender, body, date range
• sweep_simulate — preview what a cleanup pass would do
• draft_reply — compose a response to a thread
• move_message — file a message to a folder (pending user approval)

The MCP layer is what makes these available to Claude without Claude having to know anything about IMAP directly.

#How Authentication Works

Connecting an IMAP MCP server to your inbox requires credentials. There are two main paths:

OAuth: The preferred method for providers that support it (Gmail, Outlook, Zoho, Fastmail). You authorize the service in your provider's login interface. No password is shared — the provider issues a scoped access token that can be revoked independently of your main account.

App-specific passwords: Required for Yahoo, AOL, and some IMAP accounts where OAuth is not available to third-party clients. An app-specific password is generated in your email provider's account security settings — it is a separate credential, scoped to mail access only, that you can revoke at any time without changing your main password.

The important principle: a well-designed IMAP MCP server never asks for your main account password. CME follows this — you connect via OAuth or an app-specific password, and your primary credentials are never stored.

#Why Hosted Setup Matters

You could, in theory, run an open-source IMAP MCP server locally. Several exist. But self-hosting creates real friction:

• You need to run a persistent process on your machine or a server.
• You manage credential storage, token refresh, and connection errors yourself.
• The MCP URL has to be reachable by Claude — which means port forwarding or a tunnel if you are on a home network.
• You need to keep the server updated as MCP evolves.

A hosted IMAP MCP server like CME removes all of this. You authenticate once, CME maintains the connection, and the MCP URL is always live. For users who are not comfortable managing server infrastructure, hosted is the only practical option. For developers who are evaluating the technology, hosted is the fastest path to working with real inbox data.

#What CME Exposes to Claude

When you connect an inbox through CME, Claude gains access to these capabilities (depending on your plan):

• Read and search: fetch messages, search by any field, surface recent threads.
• Sweep simulation: preview a cleanup plan across hundreds or thousands of messages before anything changes.
• Write actions (Pro and above): draft, reply, send, move, delete, flag — all review-forward, meaning Claude proposes and you approve.
• Recurring scans (Pro and above): scheduled passes that surface what needs attention without you having to ask.

The tools page has the full breakdown. Pricing starts at free for a single inbox with read access.

#FAQ

#Does IMAP give Claude access to everything in my inbox?

It depends on the scopes granted. CME connects to your inbox and exposes it to Claude through structured tool calls. Claude sees what those tools return — which is controlled by CME's implementation. CME does not maintain a secondary inbox archive; it fetches messages when needed, while metadata and feature-specific retention are handled under the privacy policy.

#Is an IMAP MCP server the same as an email plugin?

Not exactly. A plugin (in the older sense) was typically a static integration with limited, predefined behaviors. An MCP server is a dynamic tool provider — Claude decides when to call each tool based on the conversation and uses the results in context. The difference is in the intelligence layer: Claude reasons about when and how to use email tools, rather than following a fixed script.

#What email providers work with IMAP MCP?

Any provider with IMAP access. CME supports Gmail, Outlook, iCloud, Yahoo, AOL, Zoho, Fastmail, and standard IMAP accounts. For providers without native OAuth support (Yahoo, AOL), an app-specific password is required.

#Do I need to understand IMAP to use CME?

No. CME handles the protocol entirely. You authenticate via OAuth or an app-specific password, and the rest is abstracted away. You interact with your inbox through natural conversation with Claude.

#Can I connect a custom domain email address?

Yes, if your custom domain email is hosted on a provider with IMAP access (Google Workspace, Zoho Workplace, Fastmail, or a standard IMAP server). Use the generic IMAP option in CME and enter your IMAP server settings.

Want to connect your own inbox? See the email tools CME makes available to Claude, review pricing for Free, Pro, and Power plans, or start with the free email cleaner to get an instant read on your inbox before committing to anything.