Skip to main content
Glama
vaemail

vaemail

Official

Related Servers

Alternatives to vaemail

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send and track transactional email, manage templates and sending domains, and read inbound email through the transactional email API.
      16
      355 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      267 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with real email: add domains with exact DNS records, create mailboxes, aliases and catch-alls, read one unified inbox across them, wait for sign-up codes and magic links, then send, reply in-thread, forward and draft. Scoped tokens with a send permission and daily cap, dry runs on every write, signed webhooks and a full audit log keep agent mail controlled.
      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.
      374 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target a distinct resource and action: send, validate, get message, list messages, bounces, usage, audit, domains. The only mild overlap is between vaemail_dns_requirements and vaemail_create_domain, since both return DNS records, but they are separated by stage: one is a general reference and the other acts on a specific newly declared domain.

    Naming Consistency4/5

    All tools share the vaemail_ prefix and most follow a clear verb_noun pattern such as list_domains, send_email, get_message, create_domain. Two tools, vaemail_capabilities and vaemail_dns_requirements, are noun-only rather than verb_noun, which is a minor deviation but does not create confusion.

    Tool Count5/5

    13 tools is well within the ideal range and appropriate for a transactional email service. Each tool covers a meaningful part of the workflow: capabilities, domain setup, sending, delivery tracking, bounce management, validation, usage, and diagnostics.

    Completeness4/5

    The tool surface covers the main transactional email lifecycle: send, validate, track, list, diagnose deliverability, manage domain verification, and review bounces. Minor gaps exist such as no domain removal or bounce management beyond listing, but agents can complete core workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues