About Send16
Send16 is an MCP server for AI agents and MCP clients to manage email operations through Send16. Its 79 tools cover sending, marketing, contacts, deliverability, inboxes, and webhooks, with a sandbox sender that needs no DNS setup.
Key features
- 01Send transactional and marketing email
- 02Manage campaigns and automations
- 03Create and organize contacts
- 04Check domains and DNS health
- 05Manage transactional replies
- 06Configure outgoing webhooks
Use cases
- 01Send an initial test email without DNS setup
- 02Schedule or batch email delivery
- 03Manage audiences and campaign segments
- 04Inspect delivery setup and webhook endpoints
MCP support
Exposes 79 Send16 tools to MCP clients over stdio or Streamable HTTP. Supports a hosted endpoint and per-request API keys.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.send16.com/mcpclaude mcp add --transport http send16 https://mcp.send16.com/mcp{"mcpServers":{"send16":{"type":"http","url":"https://mcp.send16.com/mcp"}}}Open in Cursor{"servers":{"send16":{"type":"http","url":"https://mcp.send16.com/mcp"}}}Open in VS Code{"mcpServers":{"send16":{"type":"http","url":"https://mcp.send16.com/mcp"}}}{"mcpServers":{"send16":{"serverUrl":"https://mcp.send16.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
79| Parameter | Type | Required | Description |
|---|---|---|---|
| apiKey | string | No | Send16 API key (overrides SEND16_API_KEY env var) |
Details
From the project READMEsend16-mcp
The email API your AI agent can actually use. A Model Context Protocol server for Send16 that gives Claude, Cursor, and any MCP client 79 tools to send transactional & marketing email, manage contacts, audiences, segments, automations, templates, the inbox, suppressions, and webhooks — from natural language.
It ships a zero-DNS sandbox sender, so an agent can send its first real, delivered email in seconds with no domain setup.
npx send16-mcp
Quick start
You need a Send16 API key (sk_live_…) from your dashboard. Then pick your client:
Claude Desktop / Claude Code
claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):
{
"mcpServers": {
"send16": {
"command": "npx",
"args": ["-y", "send16-mcp"],
"env": { "SEND16_API_KEY": "sk_live_..." }
}
}
}
Cursor
.cursor/mcp.json:
{
"mcpServers": {
"send16": {
"command": "npx",
"args": ["-y", "send16-mcp"],
"env": { "SEND16_API_KEY": "sk_live_..." }
}
}
}
Windsurf, VS Code, and any stdio-capable MCP client work the same way — run the send16-mcp binary with SEND16_API_KEY in the environment.
Hosted (no install)
For clients that only speak remote MCP (Claude web connectors, ChatGPT custom GPTs), point them at the hosted endpoint and authenticate with your key:
https://mcp.send16.com
One connection, your own sk_live_… key — no install, no config file.
First send in seconds — no DNS
Most email APIs make you verify a domain before you can send anything, which blocks an unattended agent on step one. Send16's sandbox sender doesn't:
- Ask the agent to call
whoami— it returns your workspace and yoursandbox_recipient(your account owner's email). - Send
from: "[email protected]"to that address. It delivers with zero DNS setup. - Verify a domain later to send to anyone.
"Send a test email from [email protected] to my account email with the subject 'It works'."
What it can do
79 tools across the platform, including:
- Email —
send_email(single/batch/scheduled/attachments), transactional templates, delivery status. - Marketing — campaigns, broadcasts, automations, segments, subscription topics.
- Contacts — create/search/list/import, audiences, tags, custom fields.
- Deliverability — domains, DNS health (SPF/DKIM/DMARC), IP warming & sending capacity.
- Inbox — read and manage transactional replies.
- Webhooks — create/list/rotate outgoing webhook endpoints (HMAC-SHA256 signed).
Every tool also accepts an optional apiKey parameter that overrides SEND16_API_KEY, so you can switch workspaces in one session.
Environment
| Variable | Required | Description |
|---|---|---|
SEND16_API_KEY | Yes | Your Send16 key (sk_live_…) |
SEND16_API_URL | No | API base URL (default: https://api.send16.com) |
SEND16_MCP_PORT | No | If set, serves Streamable HTTP (multi-tenant) instead of stdio |
Self-hosting the HTTP connector
Presence of SEND16_MCP_PORT flips the server into multi-tenant HTTP mode — each request carries its own Authorization: Bearer sk_live_…, threaded through the whole request, so one process serves many users:
docker build -t send16-mcp . && docker run -p 4242:4242 send16-mcp
Develop
npm install
SEND16_API_KEY=sk_live_... npm run dev # run from source
npm run build # bundle to dist/
Links
- Site & docs: https://send16.com · https://send16.com/docs
- npm: https://www.npmjs.com/package/send16-mcp
- Status: https://status.send16.com
License
MIT © Spruik Co
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.