mcpbeat Sign in

Dead Simple Email MCP Server

by deadsimple Your server? Claim it
answering

Dead Simple Email is answering right now. Last checked 15 min ago. 442 installs a week from pypi. It exposes 14 tools. Last commit 17 Sep 2026.

Give an agent its own inbox: send, receive, and pull signup codes from real email.

Installs per day peak 268 · avg 63 · -26% w/w
a month agotoday
Uptime history 75 days of history
75 days agonow
100.0%
Uptime 24h
91 of 91 checks
14
Tools
read from the server
422 ms
Response time
average over 24h
442
Installs / week
npm and PyPI

What the code does

We read the source, 2 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] src/deadsimple/__init__.py:1, [пакет] src/deadsimple/__main__.py:1, [пакет] src/deadsimple/cli.py:1 и ещё 12
этот файл ставится пользователю, но в репозитории его нет

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add dead-simple-email --transport http https://api.deadsimple.email/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dead-simple-email": {
      "url": "https://api.deadsimple.email/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.dead-simple-email]
url = "https://api.deadsimple.email/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dead-simple-email": {
      "url": "https://api.deadsimple.email/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "dead-simple-email": {
      "url": "https://api.deadsimple.email/mcp"
    }
  }
}

This one needs environment variables set before it will start: DSE_API_KEY (Dead Simple Email API key (starts with dse_). Get one instantly with no signup form: POST https://api.deadsimple.email/v1/auth/agent-signup). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inbox
create_inbox
Create a new email inbox. Returns the inbox details including the email address. Args: display_name: Friendly name for the inbox (e.g. "Support Bot") tags: Comma-separated tags (e.g. "support,production")
delete_inbox
Delete an inbox and all its messages. Args: inbox_id: The inbox ID to delete
verification
get_verification_code
Wait for a verification/OTP email and return the extracted code. Waits for the next new inbound email, then returns the auto-extracted verification code (and any magic link). Perfect for autonomous sign-ups. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) timeout_seconds: Max seconds to wait (default 60)
get_verification_link
Wait for an email and return the extracted magic link / verification URL. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) timeout_seconds: Max seconds to wait (default 60)
forward
forward_message
Forward a message to new recipients. Args: inbox_id: The inbox containing the message message_id: The message ID to forward to: Recipient email address (comma-separated for multiple) body: Optional additional text to include
inboxes
list_inboxes
List all email inboxes in the account. Args: limit: Maximum number of inboxes to return (default 20)
message
read_message
Read a single message with full body content. Args: inbox_id: The inbox containing the message message_id: The message ID to read
messages
read_messages
Read recent messages in an inbox. Args: inbox_id: The inbox to read from limit: Maximum number of messages to return (default 10)
reply
reply_to_message
Reply to a message. Threading headers are set automatically. Args: inbox_id: The inbox containing the message message_id: The message ID to reply to body: Reply body (plain text)
send
send_email
Send an email from an inbox. Args: inbox_id: The inbox to send from to: Recipient email address (comma-separated for multiple) subject: Email subject line body: Email body (plain text) cc: CC recipients (comma-separated, optional) bcc: BCC recipients (comma-separated, optional)
thread
read_thread
Read all messages in a conversation thread. Args: inbox_id: The inbox containing the thread thread_id: The thread ID to read
threads
list_threads
List conversation threads in an inbox. Args: inbox_id: The inbox to list threads for limit: Maximum number of threads to return (default 10)
usage
get_usage
Get account usage metrics: inboxes, emails sent/received, plan limits.
wait
wait_for_email
Block until a NEW inbound email arrives in the inbox, then return it. Use for signup/verification flows: trigger the action that sends the email, then call this to receive it. Only emails arriving after this call count. Args: inbox_id: The inbox to watch from_contains: Only match senders containing this text (optional) subject_contains: Only match subjects containing this text (optional) timeout_seconds: Max seconds to wait (default 60)

Endpoints

URLTransportStateLatencyChecked
https://api.deadsimple.email/mcp streamable-http sign-in 417 ms 15 min ago

Alternatives to Dead Simple Email

same job, measured the same way
npubmail
by npubmail

Email inbox for AI agents, owned by a Nostr key. No signup or API key. Receive codes, read, send.

local only
Agenticmail
by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

220 installs/wk local only
MailFlat
by mailflat

Real email inboxes for AI agents: open an address, read the one-time code, send mail.

380 installs/wk local only
AI Mail MCP
by aimailmcp

Real email for AI agents: domains, mailboxes, a unified inbox, wait-for-code, send and reply.

answering
send0
by send0-dev

Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.

412 installs/wk answering
Agentboxd
by agentboxd

Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.

answering
BlinkInbox
by blinkinbox

Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.

answering
A
agentsbase — Email for AI Agents
by agentsbase

Email for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes.

65 installs/wk local only

Dead Simple Email — questions

Answers built from our own checks of this server.

What can Dead Simple Email do?
It exposes 14 tools, read directly from the server on our last check. Among them: create_inbox, delete_inbox, forward_message, get_usage, get_verification_code, get_verification_link and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Dead Simple Email mostly used for?
Its tools cluster around inbox and verification. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Dead Simple Email working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 422 ms. The bar chart above shows every period we have measured.
How do I connect Dead Simple Email?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Dead Simple Email?
No API key is involved. Dead Simple Email answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Dead Simple Email?
It answers our handshake in 422 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Dead Simple Email?
The pypi package deadsimple-email was installed 442 times in the last week. Week over week that is -26%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Dead Simple Email open source?
Yes — it is published under the MIT licence, written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.