CloudMailin MCP Server

Email for AI agents

A hosted remote MCP server for your CloudMailin account. Claude, Cursor, and any MCP client can list your addresses, inspect delivery status, and send email — secured with OAuth.

OAuth 2.1 + PKCE Nothing to install No API keys
claude
did the invoice email to kate@acme.com deliver?
cloudmailin — listSentMessages(to: "kate@acme.com")
delivered · 250 2.0.0 OK · 0.42s
Yes — accepted by acme-com.mail.protection.outlook.com at 14:32 UTC.
great, send her the receipt as well
cloudmailin — sendEmail(to: "kate@acme.com", …)
queued · from billing@yourdomain.com

Connect

Pick your client. No API keys to copy around.

The server is hosted at https://mcp.cloudmailin.com/mcp — point your MCP client at it and sign in with the CloudMailin login you already have.

Claude Code
$
claude mcp add --transport http cloudmailin https://mcp.cloudmailin.com/mcp

First use opens the OAuth sign-in in your browser — run /mcp inside Claude Code if you need to re-authenticate.

Use cases

What your agent can do with it

Plain-language requests become email operations — no API integration, no polling, no copy-pasting message IDs.

“What landed at support@ this morning?”

Your agent reads the inbound feed — who wrote, what about, and whether your webhook accepted each message — and triages what needs a human.

listMessages receive & read

“Did the password reset reach kate@acme.com ?”

Instead of grepping logs, the agent answers with the delivery record — accepted, the receiving server's response, or the exact bounce reason.

listSentMessages track delivery

“Send her the receipt, and CC accounts.”

The agent writes and sends through your verified domain — markdown in, proper HTML and plain text out, tracked like every other message.

sendEmail send scope

Trusted infrastructure

Email for agents, on infrastructure that predates them

Agent email tools are appearing overnight. CloudMailin's MCP server is a thin layer over the same platform that has received and delivered billions of messages since 2010 — not a product built last quarter.

16+

Years running

99.99%

Uptime

Billions

Of emails handled

SOC 2

Type 2 audited

Tools

Four tools. The whole email loop.

Deliberately small — enough for an agent to answer "did it arrive?" and "send it", without handing over your whole account.

read

listAddresses

Every inbound address in the account, with its ID and the HTTP target it delivers to.

read

listMessages

Delivery status of email received by an address — including the response your endpoint returned.

read

listSentMessages

Outbound delivery status — delivered, deferred, or bounced, with the receiving server's SMTP response.

send

sendEmail

Send email through your verified sending domains, tracked like any other outbound message.

Security

Scoped, auditable, revocable

An agent with email access deserves the same care as a team member with email access. Grants are explicit, narrow, and yours to take away.

  • Read and send are separate scopes

    You choose at consent time — read covers addresses and delivery status, send allows sending email.

  • Owners and admins only

    Other members of the account can't authorize an MCP client.

  • OAuth 2.1 with PKCE

    The current best-practice flow — no long-lived secrets in client config files.

  • Revocable from your account page

    Revoke a grant and its tokens stop working immediately.

cloudmailin.com/…

Authorize Claude

wants access to your CloudMailin account

Account Acme Inc
Read addresses & delivery status read
Send email send
Approve Deny

Revocable any time from your account page

Using the local npm server? The cloudmailin-mcp package, which ran on your machine with an API key, is deprecated — the remote server replaces it with nothing to install and OAuth instead of keys.

Give your agents email

Sign up free, connect a client in one command, and your agent can check delivery and send email in minutes.