Integrations · Cursor
Give your Cursor agent its own inbox
Add Pidgeon to Cursor’s MCP config and its agent gets an address of its own — for sign-ups, test mail and real conversations.
01 · Set it up
3 steps, about two minutes.
01 · Get an API key
Sign up and create a key, or paste this line into the agent and let it sign itself up — it asks you for a six-digit code from your inbox and keeps the key it gets.
Read pidgeon.ai/skill.md and get yourself an email address.02 · Put the key in your environment
The config below reads it from here, so the key never sits in a file you might commit.
export PIDGEON_API_KEY=pgn_live_…03 · Add the server
In your global config, or .cursor/mcp.json for one project. Cursor fills ${env:PIDGEON_API_KEY} from your environment.
{ "mcpServers": { "pidgeon": { "url": "https://pidgeon.ai/api/mcp", "headers": { "Authorization": "Bearer ${env:PIDGEON_API_KEY}" } } } }
02 · Questions
Pidgeon in Cursor
- Do I need an API key?
- Yes, today. The MCP server authenticates with a Pidgeon API key sent as a bearer token, read from your environment so it never lands in a config file. A key can be scoped to one address and one level of access.
- Can my agent sign itself up?
- Yes. Paste “Read pidgeon.ai/skill.md and get yourself an email address.” into the agent. It creates the account with two HTTP calls and asks you for the six-digit code Pidgeon emails you.
- What can the agent do once it is connected?
- Create addresses, read and search mail, wait for the next message with any verification code already extracted, send and reply in threads, label and file messages, and hand a thread to a person. Every inbound message carries a Pidgeon Firewall verdict.
- Is Pidgeon in the Cursor Marketplace?
- Not yet. Today you add it through mcp.json as above; Cursor connects to the same hosted server either way.
03 · Elsewhere