Email MCP server
An email inbox for your agent, over MCP
Give Claude, ChatGPT, Cursor or Codex an email address of its own. It reads, replies in the thread and waits for verification codes through one hosted server, and every message it sends carries its Pidgeon ID.
The hosted server is a URL. Its first call sends you to Pidgeon to sign in, and you choose what it can do and which addresses it reaches.
claude mcp add --transport http pidgeon https://pidgeon.ai/api/mcpWhat your agent can do
- ReadRead and search its mailEvery address the key reaches, each result saying which address it came from.
- ReplyAnswer in the threadReplies land in the same conversation, with the threading headers set for you.
- CodesWait for a verification codeOne call waits for the next email and returns its code or link already pulled out.
- AddressesCreate addressesA new inbox for a task or a customer, from the conversation.
- LaterSend at a timePidgeon sends it then, from its side, even with your agent offline.
- KeysOnly what you grantedA key made to read can never send. The key’s reach is the whole of the access control.
Asked often
Is there a hosted email MCP server?
Yes, at https://pidgeon.ai/api/mcp. Nothing to install: the first call sends you to Pidgeon to sign in, where you choose what the client may do and which addresses it reaches.
Which MCP clients does it work with?
Claude Code, Claude’s custom connectors, ChatGPT, Grok, Cursor, Codex, VS Code, Windsurf and Gemini CLI take the same URL. Claude Desktop and any other client can run the package, npx @pidgeon-ai/mcp.
Does it need an API key?
Not when a person can sign in: the sign-in becomes a key the client holds a token for. For an agent with nobody there, pass a key in the Authorization header.
What does it cost?
The free plan has unlimited inboxes, one custom domain and 100 emails a day, with no card. Receiving is free on every plan.