Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-iancollins27-mailsnail": {
"args": [
"-y",
"mailsnail"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Open-source, provider-agnostic physical mail for AI agents.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mailsnail' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mailsnail against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
PubNub Model Context Protocol MCP Server for Cursor and Claude
Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers
MCP Security Weekly
Get CVE alerts and security updates for io.github.iancollins27/mailsnail and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Open-source, provider-agnostic physical mail for AI agents.
Agents have every channel except one. They can email, text, call, and post to every feed — but until now, putting a real, postmarked envelope in a mailbox meant a human signing up for a print-provider account, provisioning API keys, and wiring billing. Mailsnail closes that gap:
extra_service: "certified" — the mail that legally must be physical (preliminary lien notices, legal notices) and must not miss its deadline because one print API had a bad day.claude mcp add mailsnail -- npx -y mailsnail
# then: "Send me a postcard that says hello."
| Package | What it is |
|---|---|
mailsnail | MCP server — 7 tools (verify_address, preview_letter, send_letter, send_postcard, get_letter, list_letters, cancel_letter) over any provider below. Works in Claude Code, Claude Desktop, Cursor, Codex CLI, OpenAI Agents SDK. |
@mailsnail/core | Provider-agnostic core: adapters (Click2Mail, Lob, any Mailsnail gateway), multi-provider failover router, request validation. Zero dependencies. |
@mailsnail/gateway | Self-hostable REST API: BYO provider credentials, body_text→PDF rendering, proofs, invocation logging. The managed service at api.mailsnail.dev runs the same wire protocol. |
spec/ | The provider-neutral mail-piece schema + the failover-safety contract. Implement it and anything — including a print shop — becomes a Mailsnail-compatible node. |
| Mode | Credentials | Paying | Good for |
|---|---|---|---|
| managed (default) | none | agent, per piece (Stripe SPT) | agents; zero-setup |
| gateway | your own, on your server | your provider account | teams; PII stays in your infra |
| click2mail / lob (BYOK) | yours, local env | your provider account | direct control, one provider |
| failover chain | yours, per provider | your provider accounts | mail that must not miss deadlines |
Failover is deliberately conservative: a send moves to the next provider only when the failed provider guarantees nothing entered production and no money moved (safeToRetry — see the spec). A duplicate certified letter is worse than an error.
MAIL_MCP_ALLOW_LIVE=1.preview_letter returns a proof PDF and exact price before anything is charged — show it to your user first.You're letting software put paper in mailboxes and spend money doing it. Read the code. Run it yourself with your own provider account for free. Use managed mode when you'd rather not hold credentials at all. If we ever disappoint you, MAIL_PROVIDER=click2mail and your mail keeps moving — that's the deal, and it's enforceable because this repo exists.
Early. US-only today. Letters, c