Skip to main content
Glama
pushplus

PushPlus MCP Server

Official
by pushplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PushPlus MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP-Pushover Bridge

      pyang2045
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send push notifications to mobile devices via Pushover, allowing users to receive instant alerts for task completions, errors, reminders, and custom messages through their AI conversations.
      1
      13 npm
      2
      MIT

    • kweenkl MCP Server

      antoinedelorme
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send push notifications through the kweenkl service. Allows users to receive contextual notifications from their AI when tasks are complete or important events occur.
      1
      10 npm
      MIT

    • ntfy MCP Server

      hexerei
      A
      license
      Not graded
      quality
      D
      maintenance
      Send push notifications to mobile devices via ntfy.sh from AI assistants.
      MIT

    • mcp-notifications

      zudsniper
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables sending real-time and webhook notifications when AI agents complete tasks, with support for Discord, Slack, Teams, Feishu, Ntfy, and custom webhooks.
      6
      MIT

    • BotBell MCP Server

      qq418716640
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.
      2
      7 npm
      1
      MIT
    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.2/5.0

    Scored across 100 tools

    Disambiguation4/5

    Tools are organized by resource with detailed endpoint descriptions, so most have clearly distinct purposes. The main ambiguity is between send_push_message and the template-specific send_* helpers, and a few deprecated settings tools add noise. Overall, an agent can usually identify the correct tool without much risk of misselection.

    Naming Consistency4/5

    The dominant open_<domain>_<action> snake_case pattern is consistent and predictable across the vast majority of tools. Minor deviations like send_text_message, batch_send_message, and open_get_access_key break the pattern slightly, but they remain readable and easy to recognize.

    Tool Count1/5

    100 tools is an extreme count for a single MCP server, far beyond the 50+ threshold. Even though the underlying PushPlus API is broad, exposing every endpoint as an individual tool creates a heavy navigation and selection burden that could be reduced through domain-split servers or consolidated CRUD tools.

    Completeness4/5

    The server covers messages, tokens, settings, topics, subscribers, friends, webhooks, preprocessors, forward rules/logs, bot bindings, image uploads, and payments in depth. Minor gaps remain for mail/MP/CP channels, which only offer list/detail operations, and deprecated settings tools linger, so it stops just short of complete lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources