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
      2 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
      3 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
      10 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.1/5.0

    Scored across 107 tools

    Disambiguation3/5

    Most tools map to distinct resource+action pairs (e.g., open_token_*, open_topic_*), but several overlapping families exist: six send_* tools for templated sending, two image-upload paths (open_user_image_upload_token vs open_file_upload_image), and deprecated settings tools alongside replacements. The sheer volume increases misselection risk even when descriptions are detailed.

    Naming Consistency4/5

    Nearly all tools use snake_case with an open_ prefix and domain_action pattern, which is highly readable. The main deviation is the send_* family and batch_send_message, which omit the open_ prefix, plus minor variations like open_clawbot vs open_cmcc. Still, no chaotic mixing.

    Tool Count1/5

    107 tools is an extreme mismatch for a single MCP server, far beyond the 3-15 sweet spot and even the 25+ heavy threshold. The surface includes deprecated and convenience tools that could be consolidated, making the server overwhelming for agents.

    Completeness4/5

    The set covers a very broad PushPlus API surface: messaging, tokens, topics, topic users, friends, webhooks, settings, preprocessing, forwarding rules/logs, mail/mp/cp channels, QQ/ClawBot/CMCC bots, images, and pay. Minor gaps include deprecated settings tools and read-only mail/mp/cp channels, but core lifecycle operations are largely present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources