Pidgeon

@pidgeon-ai/mcp

An MCP server that gives your AI agent its own email inbox. Pidgeon is the email inbox API for AI agents. It gives agents their own inboxes so they can work with emails just like a human.

Over Model Context Protocol an agent can create addresses, send, wait for a reply with its verification codes already pulled out, answer in the thread, and hand a conversation to a person. There are two ways in, and they are the same server.

Hosted: a URL, and you sign in

claude mcp add --transport http pidgeon https://pidgeon.ai/api/mcp

The first call answers 401, and the client sends you to Pidgeon to sign in with OAuth. You choose what it can do — read, read and send, or full access — and which addresses it can reach. Claude's custom connectors, ChatGPT, Cursor, Codex and VS Code take the same URL and sign in the same way. Nothing to install.

For an agent with nobody there to sign in, send a key instead:

claude mcp add --transport http pidgeon https://pidgeon.ai/api/mcp \

--header "Authorization: Bearer $PIDGEON_API_KEY"

The Claude Code, Codex, Cursor and Gemini CLI plugin installs the hosted server with a skill that teaches the agent to use it: pidgeon-ai/pidgeon-plugins.

Or installed: this package

For a client that runs MCP servers as local processes.

PIDGEON_API_KEY=pgn_live_… npx -y @pidgeon-ai/mcp init

That checks the key against the API and tells you which addresses it reaches — the one question a block of JSON cannot answer, and the one that otherwise surfaces as a model quietly getting an error you never see. Then it writes .mcp.json in the current directory and prints what it wrote.

--print to see the config without writing it, which is what you want if your client keeps its own somewhere else. --force to replace an entry that is already there.

For Codex, VS Code and Gemini CLI, --client writes the hosted server into that client's own file instead:

npx -y @pidgeon-ai/mcp init --client codex    # ~/.codex/config.toml

npx -y @pidgeon-ai/mcp init --client vscode # .vscode/mcp.json npx -y @pidgeon-ai/mcp init --client gemini # .gemini/settings.json

With no PIDGEON_API_KEY it writes the URL alone and the client signs you in (codex mcp login pidgeon, /mcp auth pidgeon in Gemini CLI, a browser prompt in VS Code). With a key it checks the key first and has the client read it from the variable, or ask for it once in VS Code, so it is never in the file. It keeps everything already in the file, comments included, backs a changed file up to .bak, and is a no-op the second time. --scope user|project picks the other file; --sign-in ignores a key that is set.

The key is referenced from the environment rather than written into the file, so the config can be committed and the credential cannot:

{

"mcpServers": { "pidgeon": { "command": "npx", "args": ["-y", "@pidgeon-ai/mcp"], "env": { "PIDGEON_API_KEY": "${PIDGEON_API_KEY}" } } } }

A pgn_live_… key comes from pidgeon.ai/app/developers/keys. No account yet? An agent can sign itself up by reading pidgeon.ai/skill.md; the only thing it needs from a person is a six-digit code.

PIDGEON_BASE_URL points it somewhere else, which is how you run it against a local checkout.

Documentation: pidgeon.ai/docs/mcp.

Tools

| read_attachment | The text of one attachment — a CSV, a log, JSON, a calendar file, or a PDF, a Word .docx or an Excel .xlsx.