Skip to main content
Glama
ignytehq

plunk-mcp

Official
by ignytehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to plunk-mcp

No user-submitted related servers found.

    Related Servers

    • send16-mcp

      spruikco
      A
      license
      B
      quality
      A
      maintenance
      The email API your AI agent can actually use. A Model Context Protocol server for Send16 that gives Claude, Cursor, and any MCP client 79 tools to send transactional & marketing email, manage contacts, audiences, segments, automations, templates, the inbox, suppressions, and webhooks.
      79
      24 npm
      MIT
    • @sendraven/mcp by CommonNinja

      @sendraven/mcpofficial

      CommonNinja
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to send and manage email, read threaded replies, run campaigns and automations, and handle approvals through the Model Context Protocol from any compatible client.
      45
      479 npm
      MIT

    • MuntuAI MCP

      design-smith
      F
      license
      Not graded
      quality
      C
      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.
      -

    • @resonia/veilmail-mcp

      Resonia-Health
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that exposes Veil Mail API operations as tools for AI agents, enabling email sending, template management, audience management, and analytics retrieval through natural language.
      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
      -
    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.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: event tracking, transactional email, email verification, contact CRUD, subscribe/unsubscribe, and image upload. The only potential overlap between update_contact and subscribe/unsubscribe is clarified by different ID types (UUID vs public id).

    Naming Consistency5/5

    All tools follow a consistent plunk_verb_noun pattern with snake_case (e.g., plunk_list_contacts, plunk_create_contact). The naming is predictable and uniform across the entire set.

    Tool Count5/5

    11 tools is well-scoped for an email service MCP, covering contacts, events, email sending, verification, and image upload. It is neither too sparse nor bloated.

    Completeness3/5

    Core CRUD and essential operations are present, but the descriptions reference plunk_bulk_subscribe_contacts and plunk_bulk_unsubscribe_contacts which are not provided as tools. This creates a gap for batch operations and may mislead agents into invoking non-existent tools.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources