Skip to main content
Glama
camelmailer

CamelMailer MCP Server

Official
by camelmailer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CamelMailer MCP Server

No user-submitted related servers found.

    Related Servers

    • GetMailer MCP Server

      getplatform
      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
      12 npm
      MIT
    • Tratto MCP Server by tratto-email

      Tratto MCP Serverofficial

      tratto-email
      F
      license
      A
      quality
      F
      maintenance
      Lets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.
      2
      -

    • Quolle MCP

      Quolle-main
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send transactional emails through Quolle, including sending, batching, canceling, and checking delivery status of emails.
      5
      -

    • 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.
      72 npm
      MIT

    • Lemon Email MCP Server

      manojk0303
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to send transactional emails programmatically through the Lemon Email API. Provides simple email sending capabilities with customizable sender information, recipients, and content.
      2
      MIT
    • sendcraft-mcp by sendcraftlabs

      sendcraft-mcpofficial

      sendcraftlabs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to send emails, manage campaigns, subscribers, templates, and domains via the SendCraft email API.
      26
      10 npm
      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.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

    ActivityNo data
    ResponsivenessNo issues

    Resources