Smails MCP Server

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. It runs locally over stdio via the published package.

People connecting email tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-06-26 · ★ 33 · #29 OF 75 MAINTAINED EMAIL · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Smails

before you install - you'll need

SMAILS_API_URL

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add pexni-smails -- npx -y @smails/cli

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "pexni-smails": {
      "command": "npx",
      "args": [
        "-y",
        "@smails/cli"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @smails/cli - the @smails scope differs from the repo owner (pexni); confirm it's the project's official package

registry namespace io.github.pexni is GitHub-verified and matches the repo owner

03 · What Smails can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

cli-v0.0.12 · 2026-06-26

Same CLI as v0.0.11 (--force rename, shared createMailbox helper, encodeURIComponent). Re-released to publish the MCP registry listing after shortening the server description.

cli-v0.0.11 · 2026-06-26

CLI changes from the hardening/rename pass: · create --new renamed to create --force (replace the current mailbox) · shared createMailbox helper across the CLI and MCP server · encodeURIComponent on message ids…

cli-v0.0.10 · 2026-06-24

flag() hardening; part of mail-routing fix release.

04 · Who maintains Smails

smails is maintained by pexni. It's the only MCP server we track from this author; the repo dates to Jun 2026.

05 · Facts

category
email - ranked #29 of 75 actively-maintained email servers as of 2026-08-25.
release cadence
10+ releases in the last 90 days (latest 2026-06-26)
registry
io.github.pexni/smails (active, first published 2026-06-24 · 4 versions)
packages
npm:@smails/cli

06 · Smails FAQ

What is 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. It runs locally over stdio via the published package.

Is Smails still maintained?

Yes - as of 2026-08-25, its last commit was 2026-06-26 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Smails?

Run `npx -y @smails/cli`. The README documents one environment variable (SMAILS_API_URL) to set first. You can also paste the ready-made client config above.

Does Smails run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Smails