Skip to main content
Glama
pushengage-mcp

pushengage-mcp

Related Servers

Alternatives to pushengage-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Official MCP server for PushNotif.biz.id. Enables AI agents to register websites, generate one-line SDK snippets, and broadcast or schedule Web Push (VAPID), Android FCM, iOS APNs, In-App Popups, Live Activity Toasts, and automated RSS push notifications with real-time CTR analytics.
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables sending and managing self-hosted push notifications plus applications, clients, users, plugins, and authentication operations through a REST API, with configurable toolsets and confirmation safeguards for writes.
      550 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage OneSignal push notifications, email, SMS, and user management through natural language. Supports multi-channel messaging, segmentation, templates, analytics, and iOS Live Activities with 50+ tools for complete OneSignal API coverage.
      1
      -
    • 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.
      773 npm
      2
      Apache 2.0
    • F
      license
      B
      quality
      B
      maintenance
      Enables programmatic Reddit growth campaign management via the Engain API, including task scheduling, upvote/downvote orders, opportunity discovery, and account management.
      29
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing multi-platform social campaigns from a single blog post, including creating, listing, scheduling, publishing, and retrying campaigns with idempotency and webhook-confirmed delivery.
      7 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (auth, site, settings, segments, attributes, audience groups, notifications, analytics, campaign types). Even the list_* tools for different campaign types are clearly separated by resource name, leaving no ambiguity.

    Naming Consistency5/5

    All tools follow a consistent pattern of pushengage_<verb>_<noun>. Verbs like list, create, get, update, send, and select are used predictably, and object names are clear and uniform. This makes the set highly intuitive to navigate.

    Tool Count4/5

    27 tools is above the typical well-scoped range, but it is justified by PushEngage's broad feature set covering authentication, site management, subscriber targeting, analytics, and multiple campaign types. While slightly heavy, each tool maps to a distinct API operation and earns its place.

    Completeness2/5

    The set covers core read and create operations but lacks update/delete for many resources (segments, attributes, audience groups) and has no tools for managing individual subscribers or canceling scheduled notifications. These gaps create dead ends for agents trying to perform lifecycle management.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing