Skip to main content
Glama
theYahia

@theyahia/sendpulse-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @theyahia/sendpulse-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • mcp-postmark

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending single or batch emails via the Postmark API through an MCP server.
      59 npm
      MIT

    • mailchimp-mcp

      YerayRodri
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for full Mailchimp management: audiences, tags, segments, campaigns, templates and reporting. Enables creating, sending, scheduling campaigns, managing contacts, and retrieving reports via natural language.
      MIT
    • reflow by socialrobot-io

      reflowofficial

      socialrobot-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to create and manage durable email workflows, templates, contacts, and enrollments over MCP.
      8 npm
      2
      AGPL 3.0

    • @cyanheads/mailchimp-mcp

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Draft, test, and send Mailchimp campaigns from an MCP client with audience management, subscriber CRUD, and post-send analytics behind safe-by-default send gates.
      557 npm
      2
      Apache 2.0
    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

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct functionality: campaigns, templates, SMTP, push notifications, and mailing lists. There is no overlap; agents can clearly distinguish between sending a campaign vs a transactional email, or listing templates vs campaigns.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (list_campaigns, create_push_task). However, get_mailing_lists uses 'get' for a list operation where 'list' would be more consistent, causing a slight inconsistency.

    Tool Count5/5

    With 11 tools covering campaign management, templates, SMTP, push, and mailing lists, the count is well-scoped for a marketing automation server. Each tool serves a clear purpose without redundancy.

    Completeness4/5

    Core operations for email and push campaigns are present, but missing update/delete operations for campaigns, templates, and mailing lists. The surface covers essential workflows but leaves minor gaps for full lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources