Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Related Servers

Alternatives to Cresca MCP Server

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
      38 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.
      13
      74 npm
      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
      C
      quality
      C
      maintenance
      Enables AI assistants to send and track transactional email, manage templates, domains, webhooks, contact lists, agent mailboxes, and analytics through the EuroMail API, with mail processed in the EU.
      56
      47 npm
      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.
      122 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      46
      99 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool maps to a distinct resource+action pair, and the two send tools are clearly separated by semantics (one email to many recipients vs. many distinct emails in a batch), as are get_email vs. list_emails and update_scheduled_email vs. cancel_email. Template tools split cleanly along draft-vs-published lifecycle lines, so an agent can pick the right tool from the description alone.

    Naming Consistency5/5

    All names follow a single snake_case verb_noun convention (send_email, get_email, list_emails, create_template, publish_template, delete_template, add_contacts). The only variation is qualifying modifiers like batch and scheduled, which stay within the same pattern rather than introducing a new convention.

    Tool Count5/5

    Thirteen tools sit comfortably in the well-scoped range and each one covers a real operation: six email operations, six template lifecycle operations, and one contact import. There is no visible filler or redundant alias tool.

    Completeness3/5

    Email sending and the template lifecycle are covered end-to-end (send, batch, inspect, list, reschedule, cancel, draft, publish, delete), but the contacts surface is a single write-only add_contacts with no list/get/update/delete or suppression-list management, so an agent cannot verify or clean up contacts it imported. Suppression list handling is also only referenced implicitly, leaving notable dead ends outside the core send path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues