MailerSend MCP Server

How to connect MailerSend MCP to Claude Desktop

Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.

{
  "mcpServers": {
    "mailersend": {
      "command": "npx",
      "args": ["mcp-remote", "<YOUR_MCP_URL>"]
    }
  }
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.mailersend.com/mcp
// Claude Code (one-liner): claude mcp add mailersend <YOUR_MCP_URL> --transport http

Some MCP servers require an API key. Check the source page for setup: mcp.mailersend.com/mcp.

Does MailerSend MCP cost extra?

MailerSend ships an official MCP server that uses your existing subscription credentials.

• No separate MCP licence to buy. You pay for your MailerSend plan, the MCP server queries that account.
• Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.

MailerSend also publishes a REST API

MailerSend publishes an API, but per-tier gating wasn't extracted automatically.

What you can do with MailerSend from an AI agent

Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.

Limits and gotchas

• Official MCP server — published by MailerSend themselves, so it should track product changes.
• Fallback: the REST API works for any flow the MCP server doesn't cover.
• Auth flow: MCP servers usually inherit the underlying API auth method (api-key). Expect to configure that on first install.
• Rate limits: MCP calls count against your underlying MailerSend API quota. Burst usage from a curious agent can drain a daily allowance fast.

MailerSend MCP & API FAQ