smails MCP server
Free disposable email for AI agents: a throwaway inbox to read verification codes over MCP.
36 stars59 downloads/wk
Reviews
Write oneNobody has reviewed smails yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
smails tools (5, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
create_mailboxwrite actionCreate a new temporary email mailbox. If a mailbox already exists, pass force=true to replace it.
delete_messagewrite actionDelete a specific message
get_addressGet the current mailbox address
list_messagesList messages in the current mailbox
read_messageRead a specific message
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 92 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
What the publisher says
From the smails repository's README, as published. We do not edit it. Read it on GitHub
smails
Disposable email for humans and AI agents. An instant, anonymous throwaway inbox for sign-ups, one-time codes, and confirmations — with a REST API, a CLI, and an MCP server, so your AI agent can receive verification emails too. No signup, no password.
→ smails.dev · npx @smails/cli create
Give your agent its own inbox: plug the MCP server into Claude, Cursor, or any MCP client and it can create a mailbox and read incoming mail (verification codes, magic links) on its own.
Features
- Instant inbox — open the site and you have an address, zero clicks
- Real-time — new mail arrives over WebSocket, no polling
- Built for agents — REST API, CLI, and an MCP server share the same mailbox
- Multi-domain — pick from configurable receiving domains
- Self-cleaning — mailboxes auto-expire after 7 days of inactivity
- Serverless — Cloudflare Workers + Durable Objects (one DO per mailbox, SQLite storage)
Quick start
Web
Visit smails.dev — an inbox is created for you on first load.
CLI
npx @smails/cli create # create a mailbox (token saved to ~/.smails)
npx @smails/cli inbox # list messages
npx @smails/cli read <id> # read a message (id prefix is enough)
npx @smails/cli whoami # show the current address
npx @smails/cli create --force # replace with a fresh mailboxMCP (for AI agents)
Add the server to any MCP client (e.g. Claude Desktop, ~/.claude/mcp.json):
{
"mcpServers": {
"smails": { "command": "npx", "args": ["@smails/cli", "mcp"] }
}
}Tools: createmailbox, listmessages, readmessage, deletemessage, get_address.
REST API
# create a mailbox
curl -X POST https://smails.dev/api/mailbox
# → { "address": "...", "token": "..." }
# list messages with the returned token
curl https://smails.dev/api/mailbox/messages \
-H "Authorization: Bearer <token>"Authenticate every request (except create) with Authorization: Bearer .
How it works
Inbound mail ──▶ Cloudflare Email Routing (catch-all)
│
▼
Worker email() handler ──┐
▼
Web / CLI / MCP ──REST + WS──▶ Durable Object (one per mailbox)
├─ SQLite (messages)
├─ token auth
└─ 7-day alarm → cleanup- Each mailbox is a single Durable Object, addressed by its name; messages live in the DO's SQLite.
- The token is {address}.{secret}; the Worker routes by address, the DO verifies the full token.
- A 7-day alarm wipes inactive mailboxes; any activity renews it.
Project structure
frontend/ React Router SPA (prerendered) — Tailwind v4 + shadcn
worker/ Cloudflare Worker + Durable Objects — Hono routing, postal-mime parsing
cli/ npm package — CLI + MCP server (@smails/cli)Development
Each package is independent (pnpm). Install per package.
# frontend
cd frontend && pnpm install && pnpm dev
# worker (API + Durable Objects)
cd worker && pnpm install && pnpm devShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
Runs npx -y @smails/cli on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add smails -- npx -y @smails/cli
smails: common questions
- Is smails MCP server safe?
- Mostly: it is graded B (83/100). Read the smails safety report
- How do I install smails?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does smails need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is smails maintained?
- The last commit was 93 days ago (2026-06-26). The latest release is v0.0.12.
- What can I use instead of smails?
- Servers from other publishers that do the same job: Best Tempmail MCP server, Atomic Mail MCP server and Email Inbox API + Sending by Sendmux MCP server. Compare all smails alternatives.
Alternatives to smails
Same job from other publishers: the closest match first, then the best rated.
- Best TempmailDisposable email inboxes for AI agents: create, wait for mail, extract verification codesnot reviewedGrowingB
- Atomic MailProgrammable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.not reviewedEstablishedA
- Email Inbox API + Sending by SendmuxAI email inbox and sending tools with attachments, search, live events, and webhooks.not reviewedEstablishedA
- Tomba MCP ServerMCP server for Tomba email finder, verification, and contact enrichment APInot reviewedGrowingA
- Proton Mail (unofficial)Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAPnot reviewedGrowingB