·
Guides
Agents
MCP

Give your OpenClaw or Hermes agent a real inbox: email and calendar over MCP

OpenClaw and Hermes agents can read, triage and draft your email over MCP, whatever provider hosts it. One config entry connects your OVH, iCloud, Zoho or domain mailbox, with per-mailbox limits on what the agent is allowed to do.

The most useful thing you can hand a personal AI agent is your inbox. An agent that reads email can brief you every morning, chase the thread you forgot, file the receipts and draft the replies you never get to. OpenClaw and Hermes both made that easy on the agent side: they speak MCP, the open protocol for giving agents tools. What they cannot do is reach your mailbox, because agent runtimes ship no email connectors at all, and the Gmail OAuth trick the hosted assistants use does not exist for the address your business actually runs on.

Why agents need a hosted bridge, not a desktop one

Your agent does not live on your Mac. OpenClaw and Hermes typically run headless, on a VPS, a home server or a container, and answer you over Telegram, WhatsApp or Slack. That rules out the desktop workarounds people use with Claude Desktop: Mail.app connectors need macOS with a signed-in Mail client, and Proton-style bridges need a GUI session. A headless agent needs the opposite shape: a remote MCP server it can call over HTTPS from anywhere.

That is what anymailmcp.com is. One URL, https://anymailmcp.com/mcp, turns your mailbox into a set of tools your agent can use: search and read mail, draft and send replies, move and label messages, manage folders, read your calendar and book events. It works with the providers no one ships connectors for, from OVH, Gandi and IONOS to iCloud, Zoho, Fastmail and the cPanel box at your web host, or any custom IMAP/SMTP server. Your email stays where it is: every read is a live IMAP call, nothing is copied into a database.

Connect it to OpenClaw

OpenClaw reads MCP servers from ~/.openclaw/openclaw.json. Add the server under mcpServers and restart the gateway:

{
  "mcpServers": {
    "anymail": {
      "url": "https://anymailmcp.com/mcp"
    }
  }
}

On first use the agent triggers our OAuth flow: a browser window where you sign in and connect your mailbox with the same address and password you would type into Thunderbird. Settings are auto-detected and verified live against your mail server, and the calendar comes along automatically when your provider has one. If you drive OpenClaw with the mcporter skill, the same endpoint works there; the OpenClaw MCP docs have the current key names, which move fast in that project.

Connect it to Hermes

Hermes Agent supports MCP out of the box. Point a server entry in your Hermes config at https://anymailmcp.com/mcp, restart, and approve the connection the first time the agent reaches for a mail tool. The Hermes MCP guide shows the exact config block for your install. From there your agent on Telegram or Discord can be asked "anything from the accountant this week?" and answer from your real inbox.

Decide how much your agent is allowed to do

Handing an autonomous agent your inbox is a different decision than handing it to a chat assistant you supervise message by message. This is why access levels are set per mailbox, on our side, where the agent cannot change them:

  • Read: search, read and list only. The agent can brief and summarise but cannot change a thing.
  • Read & organize: adds drafts, filing, flags, labels, folders and calendar events, still no sending and no deletion. The agent prepares, you press send.
  • Full: everything, including sending and permanent deletion, for when the agent has earned it.

Start an autonomous agent on read or read & organize. A misfiring loop can then waste a few calls, not email your clients. Daily quotas cap the blast radius on top, credentials are AES-256-GCM encrypted and revocable in one click, and where your provider offers app passwords the connect page steers you to one, so the agent's key is never your real password.

What people run

  • A morning digest: "summarise what landed overnight, flag anything from clients" delivered to Telegram before you sit down.
  • Inbox triage on a schedule: newsletters labeled and archived, receipts filed to a folder, the rest left alone.
  • Draft-for-approval: the agent writes replies to routine requests and leaves them in Drafts for a human click.
  • Calendar sweep: appointments lifted out of confirmation emails and placed on the CalDAV calendar your provider already runs.

The free tier covers one mailbox and every read and organize tool at 15 calls a day, no card required, which is exactly enough to let an agent prove itself on the morning digest before you give it more rope. Get started free, or see what Solo adds when your agent graduates to sending.

Ready to let your assistant into your inbox?

Get started, free