Send email from n8n
One MCP node, and every workflow can send.
Remote server, nothing to install
Setup
Endpoint: https://sending.dev/api/mcp
Transport: HTTP Streamable
Header: Authorization: Bearer sk_your_api_keyCreate the API key under Settings › API Keys. The plaintext token is shown once, at creation.
The thing that catches people
Give the workflow its own API key with only the scopes it needs: an n8n workflow that loops is the most common way to burn a daily send cap.
Check it works
Ask the agent to call get_usage. It is read-only, it sends nothing, and it answers with your plan, this month's quota and the capacity limits. If you get JSON back, the install is fine.
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.
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.
