Skip to main content
Glama
Sign In
GetMailer MCP Server

GetMailer MCP Server

by getplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to GetMailer MCP Server

No user-submitted related servers found.

    Related Servers

    • ZapSMTP MCP server

      ZapSMTP MCP serverofficial

      ZapSMTP
      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.
      1,378 npm
      MIT
    • @postilon/mcp

      @postilon/mcpofficial

      postilon
      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
      MIT

    • agentisend

      fortuneflick
      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.
      28 npm
      MIT
    • RuSender MCP

      RuSender MCPofficial

      Rusender
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage email campaigns, contact lists, analytics, A/B tests, and transactional emails through natural language, using OAuth for secure connection.
      MIT
    • Unosend MCP Server

      Unosend MCP Serverofficial

      unosend
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to send emails and SMS messages through the Unosend API. It also supports email validation, domain management, and contact list operations via natural language commands.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the email sending domain. For example, add_domain vs verify_domain handle different aspects of domain management, while send_email vs create_batch address different email sending scenarios. No tools appear to overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern throughout (e.g., add_domain, create_batch, get_analytics, list_templates). The verbs are appropriate and predictable (add, create, get, list, send, verify), and the snake_case convention is uniformly applied across all 14 tools.

    Tool Count5/5

    With 14 tools, this server is well-scoped for an email sending service, covering domain management, email sending (transactional and batch), templates, analytics, and suppression lists. Each tool earns its place by addressing a distinct aspect of the workflow, avoiding both excessive bloat and critical omissions.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the email sending domain. It includes creation (add_domain, create_batch, create_template), retrieval (get_analytics, get_batch, get_email, list_* tools), and operational actions (send_email, verify_domain, add_to_suppression). No obvious gaps exist; agents can manage the full email workflow from setup to analytics.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources