Skip to main content
Glama
ignytehq

plunk-mcp

Official
by ignytehq

Related Servers

Alternatives to plunk-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      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
      41 npm
      MIT
    • 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
      1,022 npm
      1
      MIT
    • 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.
      -
    • 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
    • F
      license
      A
      quality
      F
      maintenance
      Lets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.
      2
      -

    TDQS

    A4.2/5.0

    Scored across 94 tools

    Disambiguation4/5

    Individual descriptions are unusually disciplined, each with explicit 'Not for' cross-references that separate close neighbors (add vs insert_workflow_step, refresh_segment_count vs compute_segment, get_import_status vs get_bulk_job_status). However, with 94 tools there remains real overlap among the analytics family (get_campaign_stats vs get_top_campaigns vs get_campaign_breakdown vs get_activity_stats vs get_analytics_timeseries) that an agent could easily misselect.

    Naming Consistency5/5

    Virtually every tool follows the same plunk_verb_noun snake_case convention with the verb leading (list_, get_, create_, update_, delete_, send_, bulk_). Modifiers are applied consistently (bulk_ prefix, list_X_contacts/list_X_members patterns), so the naming is highly predictable throughout.

    Tool Count2/5

    94 tools is far beyond the 25+ threshold the rubric treats as too many; the surface is heavily fragmented into many narrow single-purpose calls (separate archive/unarchive/bulk_archive, separate import vs bulk job status). While the email-marketing domain is broad, this volume will strain an agent's tool-selection budget.

    Completeness5/5

    Coverage is exhaustive: full CRUD and lifecycle operations for contacts, campaigns, segments, templates, workflows, events, domains and analytics, plus imports, bulk operations, activities and upcoming sends. Almost no obvious lifecycle gaps or dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive