smails
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
smails
Disposable email for AI agents. Your agent creates an inbox, signs up somewhere, and waits for the verification code or magic link — over a remote MCP server, a local MCP server, a CLI, or plain HTTP.
Looking for a throwaway inbox for yourself, in the browser? Use smail.pw.
Use it
Fastest — paste this into Claude Code or Codex. The agent reads setup.md, adds the server, and tells you when to sign in with GitHub:
Set up smails for me by following https://smails.dev/setup.mdClaude Code — then run /mcp to sign in:
claude mcp add --transport http --scope user smails https://smails.dev/mcpCodex
codex mcp add smails --url https://smails.dev/mcp
codex mcp login smailsCLI
npx @smails/cli login # once: confirm in the browser
npx @smails/cli create # → brave-otter-k3j9x2m8@smails.dev
npx @smails/cli wait --subject code # blocks until the email arrives, prints itFree: 20 new mailboxes per account per day; each lives for 7 days. Receive-only.
Related MCP server: useblip/email
How it works
┌──────────────────────── Worker (smails.dev) ───────────────────────┐
CLI / local MCP ─┤ /api/* mail API (Bearer token, verified by signature, no lookup) │
remote MCP ──────┤ /mcp MCP Streamable HTTP, stateless │
browser ─────────┤ OAuth 2.1 server + device login, GitHub as the identity provider │
Email Routing ───┤ email() raw → R2, metadata → D1, then notify InboxHub │
└───────────┬───────────────┬──────────────┬──────────────┬──────────┘
D1 core D1 mail R2 raw mail InboxHub (one DO,
users, tokens, message (never hibernating
mailboxes, metadata deleted) WebSockets)
quotaSign-in is required. Remote MCP clients use OAuth 2.1 with PKCE (Client ID Metadata Documents or dynamic registration); the CLI and local MCP use device authorization (RFC 8628). Both get the same tokens.
Cheap per mailbox. Creating a mailbox is one row; access tokens are verified by signature, so API calls never read KV or D1 to authenticate. Mail metadata (~250 bytes) goes to D1, the raw message to R2, and nothing is deleted.
Waiting is push, not polling.
waitconnects to a single hibernating Durable Object before checking D1, so it returns the moment mail arrives and costs one request however long it waits.Addresses carry a checksum, so mail to addresses we never issued is dropped without a write.
The full design and the reasoning behind it: docs/rewrite-design.md.
Repository
site.config.ts names and ids (domain, Worker, D1, R2) — the only place they are written
web/ site: Solid 2 + StyleX, prerendered to static files
worker/ Cloudflare Worker: API, MCP, OAuth, email handler (cloudflare.config.ts + cf CLI)
cli/ @smails/cli: CLI and stdio MCP server (no runtime dependencies)
docs/ design and launch notesDevelopment
Node.js 22.18+ and pnpm.
pnpm install
cp worker/.env.example worker/.env # local signing secrets; GitHub keys optional
pnpm --filter smails-web run build # the worker serves web/dist/client
pnpm --filter smails-worker run dev # http://localhost:8792 (D1/R2/DO simulated locally)Without a GitHub OAuth App, sign in locally at
http://localhost:8792/__dev/login?login=you&next=/account. That route exists only in dev builds.Simulate inbound mail:
curl -X POST "http://localhost:8792/cdn-cgi/local/email?from=a@example.com&to=<address>" --data-binary @message.emlPoint the CLI at it:
SMAILS_URL=http://localhost:8792 node cli/dist/index.js login
pnpm run check # types + oxlint + oxfmt
pnpm -r run test # unit tests + end-to-end tests against a real workerd dev serverDeployment
Two independent tracks.
Worker + site — deployed by hand with the cf CLI (see docs/launch.md for the first launch):
cd worker
pnpm run deploy # build web + worker, apply D1 migrations, cf deployCLI (@smails/cli) + MCP registry listing — bump cli/package.json, push, then gh release create cli-vX.Y.Z --target main. The release triggers .github/workflows/publish-cli.yml (npm with provenance, then the MCP registry from server.json; its description must stay ≤ 100 characters).
Operations: pnpm --filter smails-worker run users | stats | ban <login> | unban <login>.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Real email inboxes for AI agents: register, receive, read and send mail over MCP. Free to receive.
Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.
Disposable email inboxes for AI agents: create an address, wait for the OTP or verify link.
Disposable email inboxes for AI agents — read messages and verification codes.
Related MCP Servers
- AlicenseBqualityCmaintenanceDisposable email MCP server for autonomous AI agents. Create labeled temporary inboxes, wait for verification emails, extract OTP codes and confirmation links — zero human intervention required.6MIT
- AlicenseAqualityBmaintenanceMCP server for disposable email — create inboxes, receive emails, and extract OTP codes. Let your AI agent sign up for services, wait for verification emails, and extract codes autonomously.753 npm1MIT
- AlicenseAqualityCmaintenanceProvides temporary email services for AI agents, enabling closed-loop verification of email-based registration flows with multi-provider support, auto-registration, and verification code extraction.1010 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.421 npm1MIT