Skip to main content
Glama
sendcraftlabs

sendcraft-mcp

Official
by sendcraftlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sendcraft-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • SendGrid MCP Server

      bhoggard
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send emails and manage contacts through SendGrid's Web API v3.
      -
    • @sendbyte/mcp by Sendbyte-Africa

      @sendbyte/mcpofficial

      Sendbyte-Africa
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.
      11
      13 npm
      MIT

    • SendGrid MCP Server

      FINCH285
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to send emails, manage contacts, and interact with SendGrid's email platform via MCP.
      1
      MIT

    • MuntuAI MCP

      design-smith
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.
      -
    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 26 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action, with clear differentiation between transactional and campaign sending, and between list/get operations for different entities. Potential overlaps are resolved by specific descriptions.

    Naming Consistency4/5

    All tools follow the sendcraft_ prefix and mostly use verb_noun structure. Minor deviations like 'unsubscribe' (verb-only) and 'batch_send' (verb at end) are still understandable and do not break the overall pattern.

    Tool Count2/5

    With 26 tools, the server exceeds the 25-tool threshold and feels overly heavy. Many list/get tools could be consolidated, and the count makes the toolset harder to navigate.

    Completeness3/5

    Core operations for sending, scheduling, and tracking are covered, but update/delete operations are missing for campaigns, templates, domains, and subscribers. Subscriber management relies on add/unsubscribe only, and there is no way to modify or remove certain resources, leading to notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources