mcpemails
Sign inGet started free

Give your AI
agent an inbox.

Connect Gmail, Outlook, or any IMAP account once. Paste a single MCP endpoint URL into Claude, Cursor, or any MCP-compatible agent. Your agent can now read, search, and send mail — live, with no email stored on our servers.

Connect your inboxRead the docs
100 free calls / month No card required Email never stored
How a call flows
t+0ms → t+312ms
AI agent
Claude · Cursor · n8n
MCP
mcpemails
/mcp endpoint
IMAP
Your provider
Gmail · IMAP
live · t+12mslist_inbox()
→ agent calls list_inbox(account="work-gmail")
· mcpemails fetches via Gmail API (token rotated)
← 20 messages returned · nothing stored
mcpemails (the pipe) live request your data, your provider
Works with every MCP-compatible agent and client
Claude DesktopCursorn8nZedWindsurfContinue
Principles

Six things we believe
about email and agents.

The decisions that shaped the product. If any of them stop being true, that's a bug worth filing.

  1. 01Scope

    Five tools. The whole surface area.

    Every email task your agent needs fits in five calls: list_inbox, read_email, search_emails, send_email, reply_to_email. Add the MCP endpoint URL to any compatible agent. That's the entire integration.

  2. 02Storage

    Email is fetched live. Never stored.

    Every tool call hits your provider in real time — Gmail API, Microsoft Graph, or IMAP. Message bodies, subjects, and attachments are returned to the agent and immediately discarded. The only thing we persist is an encrypted OAuth token per inbox, so we can make the next call.

  3. 03Sending

    Sending goes through your provider.

    When your agent calls send_email or reply_to_email, the message is dispatched via the Gmail API, Microsoft Graph, or your own SMTP server. Your domain reputation and deliverability stay entirely in your hands. We never relay mail from our own domain.

  4. 04Providers

    Gmail, Outlook, or any IMAP inbox.

    OAuth 2.0 for Gmail and Outlook. App passwords for Fastmail and any IMAP/SMTP provider. Connect multiple inboxes — label them by use case (work-gmail, ops-outlook, support-fastmail) and scope each API key to the inboxes you want that agent to reach.

  5. 05Access

    Standard OAuth for agents and clients.

    MCP clients authorize via a standard OAuth 2.0 flow. Scopes are per-inbox and per-permission. You review and approve access in the dashboard, and revoke any client in one click. API keys are prefixed, hashed, and never stored in plaintext.

  6. 06Security

    Credentials are encrypted at rest.

    OAuth tokens and app passwords are AES-256-GCM encrypted before being written to the database. Decryption happens only inside an isolated server function at call time. The encryption key is stored in a separate secrets vault, not alongside the data.

How it works

You're the user. We're the pipe.

Three steps from sign-up to your agent reading and sending mail.

01

Connect your inbox

Sign in and click Connect Inbox. Choose Gmail or Outlook and complete the OAuth flow — no passwords shared. For Fastmail or any IMAP provider, paste an app password instead.

02

Create an API key and add the MCP URL

Generate a scoped API key in the dashboard. Paste the MCP endpoint URL and that key into Claude Desktop, Cursor, n8n, or any MCP-compatible client. One config, all five tools.

03

Your agent works the inbox

The agent calls tools like search_emails() or reply_to_email(). MCPEmails fetches live from your provider and returns the result. Nothing is cached between calls.

list_inbox()
List recent messages with sender, subject, date, and snippet — up to 100 per call.
read_email()
Fetch a single message by ID. Returns parsed plain-text and sanitized HTML body, plus attachment metadata.
search_emails()
Provider-native search: Gmail query syntax, IMAP SEARCH, or Microsoft Graph. Returns up to 100 matches.
send_email()
Send a new message via the connected account. Dispatched through Gmail API, Graph, or SMTP — your domain, your deliverability.
reply_to_email()
Reply in-thread with correct Message-ID and References headers. Works across Gmail, Outlook, and IMAP.
"It took me longer to log into Gmail than to wire up my agent. The fact that I never had to think about IMAP credentials — or whether my email is being stored somewhere — is the entire point."
Maya Chen · staff engineer, building agent workflows at a Series C fintech
Pricing

Pay for the calls your agent makes.

Simple, transparent pricing. Switch plans any time. EU and US billing in local currency.

Free

$0 /forever

For personal projects and tinkering with agents.

  • 1 connected inbox
  • 100 MCP calls / month
  • Gmail, Outlook, IMAP
  • 1 API key
  • Community support
Start free

Pro

$29 /month

For teams shipping agents that work the inbox every day.

  • 10 connected inboxes
  • 20,000 MCP calls / month
  • Gmail, Outlook, IMAP
  • 10 API keys
  • Usage analytics dashboard
  • Email support
Start free trial

Enterprise

Custom

For organisations that need unlimited scale and compliance guarantees.

  • Unlimited inboxes
  • Custom MCP call volume
  • Gmail, Outlook, IMAP
  • Unlimited API keys
  • Audit log + SSO
  • Dedicated Slack support
  • Custom SLA
Talk to sales

All plans: email is fetched live and never stored. OAuth tokens encrypted at rest. See full feature comparison →