Integrations · VS Code
Give GitHub Copilot in VS Code its own inbox
Add Pidgeon to VS Code’s MCP config and Copilot’s agent mode gets an address of its own. VS Code asks for the key once and stores it securely.
01 · Set it up
2 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 · Add the server
In your workspace’s .vscode/mcp.json. VS Code prompts for the key the first time and keeps it in its secret storage, so nothing is written to the file.
{ "inputs": [ { "type": "promptString", "id": "pidgeon-key", "description": "Pidgeon API key", "password": true } ], "servers": { "pidgeon": { "type": "http", "url": "https://pidgeon.ai/api/mcp", "headers": { "Authorization": "Bearer ${input:pidgeon-key}" } } } }
02 · Questions
Pidgeon in VS Code
- 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.
03 · Elsewhere