CamelMailer MCP Server
OfficialRelated Servers
Alternatives to CamelMailer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.14MIT

Vaartix MCP serverofficial
AlicenseAqualityBmaintenanceEnables AI tools such as Claude and Cursor to send, batch, look up, list, and cancel transactional emails, and to check delivery status and event timelines through the underlying email API.7316 npmMIT
Tratto MCP Serverofficial
AlicenseAqualityDmaintenanceLets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.2MIT- AlicenseAqualityBmaintenanceEnables AI assistants to send transactional email, check delivery status, manage templates, and add contacts through a public email API.13MIT
- AlicenseAqualityBmaintenanceEnables AI agents to send transactional emails through Quolle, including sending, batching, canceling, and checking delivery status of emails.623 npmMIT

@postilon/mcpofficial
AlicenseAqualityCmaintenanceEnables AI assistants to send and track transactional email, manage templates and sending domains, and read inbound email through the transactional email API.1638 npmMIT
TDQS
Scored across 38 tools
Most tools target a distinct resource and action, and descriptions explicitly disambiguate near-overlaps like send_campaign_now vs send_campaign and send_to_stream vs create_campaign_draft. A few pairs, such as get_email vs get_inbound and list_emails vs list_bounces, could still cause misselection if an agent is not careful.
The naming is predominantly lowercase snake_case verb_noun, e.g. list_campaigns, create_layout, update_stream, cancel_campaign. Minor deviations like dmarc_summary, send_campaign_now, and send_email_with_template break the exact pattern but remain readable and predictable.
At 38 tools, this is well beyond the typical 3-15 tool sweet spot and above the 25-tool threshold for a heavy surface. Although the tools are organized into logical domains, the sheer number makes navigation and selection harder for an agent.
The surface is broad, covering transactional sends, campaigns, streams, subscribers, layouts, inbound handling, and stats, but template management is read-only: list_templates and render_template exist with no create_template/update_template/delete_template. There are also lifecycle gaps like no delete_campaign, delete_stream, or unarchive_stream.