API key or OAuth

Send email from Claude Code

Send email from the terminal, inside the session you are already in.

Remote server, nothing to install · config in .mcp.json or ~/.claude.json

Setup

Add the server

claude mcp add --transport http sending https://sending.dev/api/mcp \
  --header "Authorization: Bearer sk_your_api_key"

Check it

claude mcp list

Or configure it by hand

{
  "mcpServers": {
    "sending": {
      "type": "http",
      "url": "https://sending.dev/api/mcp",
      "headers": { "Authorization": "Bearer sk_your_api_key" }
    }
  }
}

Create the API key under Settings › API Keys. The plaintext token is shown once, at creation.

The thing that catches people

Claude Code · gotcha

The `type` field is not optional: an entry with `url` but no `type` is read as an stdio server and skipped silently. And if the header is present but the key is wrong, Claude Code reports the connection as failed instead of falling back to OAuth: remove the header to use consent.

Check it works

`claude mcp list` must answer `✔ Connected`.

What it can do once connected

71 tools: send transactional email and campaigns, manage contacts and lists, build and activate automations, run an inbox that receives and replies, and read back why a message never went out. All of it inside verified domains, suppression, idempotency, spend caps and an audit log, enforced on our servers rather than in the prompt.

All 71 tools · MCP docs

Other clients

Claude Desktop

Give Claude an email stack without pasting a secret anywhere.

claude.ai

The same connector, in the browser.

ChatGPT

Custom connectors, and the API path where a key still works.

Cursor

Email tools in the editor where you are writing the app that sends them.

VS Code

GitHub Copilot with a mailer attached, and the key never committed.

Windsurf

Through the mcp-remote bridge, because Windsurf speaks stdio.