MCP server
camelmailer-mcp is a Model Context Protocol server that lets AI assistants like Claude send and inspect transactional email. Nine tools, wired against the cloud or any self-hosted instance.
Claude Desktop
Add the server to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude Desktop:
claude_desktop_config.json
{
"mcpServers": {
"camelmailer": {
"command": "npx",
"args": ["-y", "camelmailer-mcp"],
"env": {
"CAMELMAILER_API_KEY": "cm_xxxx"
}
}
}
}Claude Code
terminal
claude mcp add camelmailer -e CAMELMAILER_API_KEY=cm_xxxx -- npx -y camelmailer-mcp
The nine tools
| Tool | What it does |
|---|---|
send_email | Send an email with html_body / text_body |
send_email_with_template | Render a stored template against variables and send |
list_emails | List messages (filter by scope, status, tag, query, stream) |
get_email | One message incl. SMTP delivery attempts |
list_templates | All stored message templates |
render_template | Preview a rendered template without sending |
get_stats | Message counters (sent, bounced, opens, clicks, …) |
list_bounces | Bounced messages |
dmarc_summary | DMARC pass rate and top sending sources |
Then just ask: "Send a plain-text email from billing@acme.com to ada@example.com thanking her for the purchase."
Self-hosted instances
Add CAMELMAILER_BASE_URL to the server's env (defaults to https://app.camelmailer.com):
env
"env": {
"CAMELMAILER_API_KEY": "cm_xxxx",
"CAMELMAILER_BASE_URL": "https://mail.example.com"
}API failures come back as tool errors carrying the stable CamelMailer error code, so the assistant can react. The server keeps running.
