Dead Simple Email MCP Server

email.deadsimple/dead-simple-email

answering

Dead Simple Email is answering right now. Last checked 12 min ago. 639 installs a week from pypi. It exposes 14 tools. Last commit 30 Jul 2026.

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

Installs per day peak 360 · avg 52 · +110% w/w

a month agotoday

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

660 ms

Response time

average over 24h

639

Installs / week

npm and PyPI

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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"
    }
  }
}

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_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

URL	Transport	State	Latency	Checked
https://api.deadsimple.email/mcp	streamable-http	answering	420 ms	12 min ago

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 660 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.

Does Dead Simple Email need an API key?

No. Dead Simple Email completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Dead Simple Email?

It answers our handshake in 660 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. 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 639 times in the last week. Week over week that is +110%. 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 and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.