Dead Simple Email MCP server

Which servers in the official MCP registry are Dead Simple Email's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-10

← Back to Dead Simple Email

Whose server it is

Registry nameemail.deadsimple/dead-simple-emailverified in the MCP registry

The registry name sits under deadsimple.email. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-10

Staterequires sign-inchecked 2026-10-10

On 2026-10-10 the server answered and asked for a sign-in with a Dead Simple Email account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "dead-simple-email": {
      "type": "http",
      "url": "https://api.deadsimple.email/mcp"
    }
  }
}

The first time it connects, the client opens a Dead Simple Email sign-in.

Also shipped through: oci, pypi

OpenAPI spec

109 paths, read 2026-10-10. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.