emails.sh MCP server.

It lets a coding assistant operate an emails.sh account while it writes the integration: add and verify a sending domain, mint a key, send a test message, read the delivery log, and work out why an email did not arrive.

The endpoint is https://mcp.emails.sh and speaks Streamable HTTP. Authenticate with an esh_ key from https://emails.sh/dashboard/api-keys, or authorize over OAuth in a client that supports it, in which case no key is written to disk.

Claude Code:
  claude mcp add --transport http emailssh https://mcp.emails.sh \
    --header "Authorization: Bearer esh_your_key_here"
  Leave the header off to authorize over OAuth in the browser instead.

Cursor (.cursor/mcp.json), VS Code (.vscode/mcp.json), Claude Code project config (.mcp.json):
  {
    "mcpServers": {
      "emailssh": {
        "type": "http",
        "url": "https://mcp.emails.sh",
        "headers": { "Authorization": "Bearer esh_your_key_here" }
      }
    }
  }

Restart the client after writing the file, and make sure the file is gitignored: it holds a live key.

Full setup notes: https://emails.sh/docs/mcp