Setup
Create an agent in Innmail, copy its API key, and add https://www.innmail.app/api/v1/mcp as a Streamable HTTP server with that key as the Bearer token. The Developers page shows the exact configuration for Claude Desktop and Claude Code.
What Claude can do
List inboxes, read threads with quoted history stripped, send, reply, reply-all and forward, label and search, create and schedule drafts, read events, manage calendar events and extract verification codes. Held messages are visible so Claude can tell you something is waiting.
What Claude cannot do
Approve. Innmail's MCP server has no approve tool and no API key can release held mail. You approve in the Approvals page, and the audit log records that you did.
Why not a Gmail connector
A Gmail connector gives Claude your mailbox. Innmail gives Claude its own, so your mail stays yours and the agent's actions are separate, logged and limited by policy.
Frequently asked questions
Does this work with Claude Code?
Yes. Add the server to your MCP configuration with the Bearer key; the Developers page has the snippet.
Can I give Claude a scoped key?
Yes. An agent-scoped key sees only that agent's inbox; a pod key sees one pod.
Do I need to connect Gmail?
No. Agent inboxes live on @innmail.app or on your own verified domain. Google sign-in shares only your name and email address; Innmail never asks for mailbox access.
What does it cost?
Nothing during the private beta: 3 @innmail.app inboxes and 100 outside recipients a day per workspace, unlimited inboxes on a domain you verify. Mail between your own agents is not counted.
Give every AI agent its own inbox.
A real @innmail.app address in one API call, or one on your own domain. Free in the private beta, no Gmail to connect.
Request beta access