sendsend.email
Sign inStart building

MCP server

Let an AI assistant use SendSend: send and look up email, verify addresses, and read your metrics, with nothing to install.

Connect

The server is at https://api.sendsend.email/mcp and takes your API key as a bearer token. Use a ss_test_ key to try it: nothing is delivered. Check your assistant’s own documentation if its settings look different from these.

claude mcp add --transport http sendsend https://api.sendsend.email/mcp \
  --header "Authorization: Bearer ss_test_..."
{
  "mcpServers": {
    "sendsend": {
      "url": "https://api.sendsend.email/mcp",
      "headers": { "Authorization": "Bearer ss_test_..." }
    }
  }
}
{
  "servers": {
    "sendsend": {
      "type": "http",
      "url": "https://api.sendsend.email/mcp",
      "headers": { "Authorization": "Bearer ss_test_..." }
    }
  }
}

Keep it safe

  • Read-only mode. Add ?mode=read-only to the address and every tool that sends or changes anything is left out.
  • Scoped keys. The assistant can do only what the key can. Create a key with just the scopes it needs.
  • Live keys really send. Confirm recipients and content before the assistant sends from a live key. An assistant that reads untrusted text can be tricked into emailing someone.
  • Nothing is stored. Each request carries your key and is answered on its own. The server keeps no sessions.

Tools

Look up: get_email, list_emails, list_domains, get_metrics, list_suppressions, list_webhooks, list_webhook_deliveries, list_broadcasts, get_broadcast_stats, list_broadcast_links and verify_email. Change things: send_email, add_suppression, create_webhook, delete_webhook, replay_webhook_delivery and duplicate_broadcast.

Run it yourself

The same server is on npm as @sendsendemail/mcp if you prefer to run it locally: npx -y @sendsendemail/mcp with SENDSEND_API_KEY set.