Skip to main content
Glama
CamelMailer MCP Server

CamelMailer MCP Server

Official
by camelmailer

Related Servers

Alternatives to CamelMailer MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.
      14
      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
      316 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Lets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional emails through Quolle, including sending, batching, canceling, and checking delivery status of emails.
      6
      23 npm
      MIT
    • 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
      38 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 38 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues