@postilon/mcp
OfficialRelated Servers
Alternatives to @postilon/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.1320 npmMIT

ZapSMTP MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to send, receive, and track email and manage templates, domains, webhooks, and other email API operations from AI assistants.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.28 npmMIT
- AlicenseCqualityCmaintenanceEnables AI assistants to send and track transactional email, manage templates, domains, webhooks, contact lists, agent mailboxes, and analytics through the EuroMail API, with mail processed in the EU.56403 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables sending transactional emails individually or in batches, checking delivery status, and monitoring domain email reputation metrics. It supports email tracking with tags and custom metadata.MIT
- AlicenseAqualityDmaintenanceEnables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.1428 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct resource+action pair, and the resource is explicit in the name (email, inbound, template, domain). Overlaps like send_email vs send_batch or get_email vs get_inbound are disambiguated by the descriptions (single vs up to 100 recipients, sent vs received). No two tools appear to do the same thing.
All 16 tools follow a strict snake_case verb_noun pattern (list_/get_/create_/update_/delete_/send_/cancel_/verify_ + resource). The only slight oddity is send_batch naming the shape rather than the object, but it still reads naturally alongside send_email.
16 tools sits at the upper end of comfortable but is justified by four distinct sub-domains (templates, sending, sent-mail inspection, domains, inbound). Each tool maps to a real workflow step, with no filler. Just slightly heavier than ideal.
Templates have full CRUD, emails cover send/get/list/cancel, and domains cover add/list/get/verify. The notable gap is domain lifecycle teardown (no delete_domain or update_domain), and inbound/email data is read-only, but core transactional workflows have no dead ends.