Skip to main content
Glama
@postilon/mcp

@postilon/mcp

Official
by postilon

Related Servers

Alternatives to @postilon/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.
      13
      74 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      1,270 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to send, receive, and track email and manage templates, domains, webhooks, and other email API operations from AI assistants.
      122 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect verified sending domains and submit transactional emails through hosted tool discovery, schema validation, and policy-governed execution using a single gateway API key.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      46
      MIT

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues