Pidgeon

Name: Pidgeon
Author: pidgeon-ai

by pidgeon-aiversion 0.28.1i★ –iComputer or cloud

Registry nameai.pidgeon/mcp

Install

Overview

Description from the maker (original English)

Email inbox and verifiable ID for your agent: addresses, threads, sending and replies.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Chat & email
You need to fill in: PIDGEON_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: PIDGEON_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add --transport http pidgeon https://pidgeon.ai/api/mcp --header 'Authorization: Bearer {pidgeon_api_key}'

Or run it on your computer

claude mcp add pidgeon --env PIDGEON_API_KEY=your-value -- npx -y @pidgeon-ai/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pidgeon": {
      "url": "https://pidgeon.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer {pidgeon_api_key}"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pidgeon": {
      "type": "http",
      "url": "https://pidgeon.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer {pidgeon_api_key}"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pidgeon": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pidgeon-ai/mcp"
      ],
      "env": {
        "PIDGEON_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

PIDGEON_API_KEY secret required env
Your Pidgeon API key (pgn_live_…). Make one under Developers → API keys, or let an agent sign itself up: https://pidgeon.ai/skill.md
Authorization secret required HTTP header
Your Pidgeon API key as a bearer token

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pidgeon.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 1790 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1772 servers in this category
Published to the registry more recently than 93% of the other 1772 servers in this category
Basic checks equal to or better than 100% of the other 1772 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pidgeon safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PIDGEON_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.28.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

Tool	What it does
`get_setup`	Call this first.
`list_addresses`	The addresses this credential can reach.
`create_address`	Create an address for an agent to use.
`get_address`	One address, by id.
`list_threads`	Conversations in one address, newest first.
`get_thread`	One conversation, by id.
`list_messages`	The messages of one conversation, oldest first — the text to read before replying.
`search_messages`	Full-text search across every address this credential can reach, ranked by relevance.
`send_message`	Send from an address this credential may send as.
`check_message`	Asks whether `send_message` with these arguments would go, and sends nothing.
`verify_sender`	Checks a raw message, or its headers, and answers whether an AI agent sent it, on whose behalf, and whether the signatures on it hold: the signed agent declaration (`Agent-of`) and the `Post-Envelope`, from Pidgeon or any other signer using the same formats.
`get_message`	One message, by id, with its body, the headers we keep, and what the sending domain’s records proved — `authentication.spf`, `.dkim`, `.dmarc`, where null means not reported rather than failed, and `.signature: "pass"` when another Pidgeon address sent it, signed and checked before it was stored.
`await_message`	Waits until a message arrives at an address — after you submit a sign-up form, say — and returns it with `extracted.codes` and `extracted.links`: verification codes and confirm links, most likely first.
`reply_to_message`	The recipients, the subject and the thread are read off the message being answered, so you bring the words and nothing else.
`forward_message`	Sends one message on to somebody it was not addressed to, with its attachments, from the address that received it.
`create_draft`	Writes a message without sending it, for a human to read and send — use it when you are asked to prepare replies for sign-off.
`get_draft_approval`	Where a held send stands, by its `draft_id`: `pending` until a person approves or rejects it in the dashboard, then `approved` (it was sent, and `message_id` is the message), `rejected`, or `expired` after 24 hours with nobody deciding.
`list_drafts`	Every draft at one address, newest first, with its recipients and body — so you can come back to one and finish it.
`get_draft`	One draft by id: its sender, recipients, subject, text and attachments.
`update_draft`	Changes the fields you pass and leaves the rest; `null` clears the subject or text.
`delete_draft`	Deletes one draft, and cancels its send if it was scheduled.
`schedule_draft`	Sends one draft later, from Pidgeon’s side, with no further call: it goes even if you and the person are offline.
`unschedule_draft`	Takes a scheduled draft off the schedule.

| 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.

Only the beginning is shown; read the rest in the repo

Pidgeon

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

@pidgeon-ai/mcp

Hosted: a URL, and you sign in

Or installed: this package

Tools