Send email from claude.ai
The same connector, in the browser.
Remote server, nothing to install
Setup
https://sending.dev/api/mcpCreate the API key under Settings › API Keys. The plaintext token is shown once, at creation.
The thing that catches people
Permissions are chosen on the consent screen, not by the client: MCP clients do not know our scope catalogue and usually ask for identity only. Tick nothing and every tool answers `forbidden`.
Check it works
Ask it to call `get_usage`.
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.
Other clients
Claude Code
Send email from the terminal, inside the session you are already in.
Claude Desktop
Give Claude an email stack without pasting a secret anywhere.
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.
