Skip to main content
Glama
pushplus

PushPlus MCP Server

Official
by pushplus

Related Servers

Alternatives to PushPlus MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      20 npm
      2
      MIT
    • 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
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Send push notifications to mobile devices via ntfy.sh from AI assistants.
      MIT
    • 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
    • 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
      6 npm
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 96 tools

    Disambiguation3/5

    Most tools target distinct resources (webhook, topic, friend, token, message, pre, forwardRule, qqBot, etc.), which aids separation. However, there are overlapping pairs like open_forward_rule_get_setting and open_forward_rule_save_setting (same GET endpoint, opposite semantics), two image-upload paths (open_user_image_upload_token vs open_file_upload_image), and lingering deprecated tools (open_setting_get_user_settings, open_setting_change_default_channel) that duplicate newer ones, creating avoidable confusion.

    Naming Consistency3/5

    Names are snake_case but the ordering is mixed: most follow resource_action (open_webhook_delete, open_topic_add), while others invert to action_resource (open_get_access_key, open_setting_change_is_send) or use verb phrases (open_setting_change_open_message_type). The send_* family also drops the open_ prefix, and domain nesting (open_topic_user_*, open_forward_rule_*) is applied unevenly, so the pattern is readable but not predictable.

    Tool Count1/5

    96 tools is an extreme mismatch for the scope, far exceeding the 3-15 sweet spot. Many are rare settings toggles and deprecated endpoints that could be consolidated, making the surface overwhelming for an agent to navigate.

    Completeness4/5

    The surface broadly covers the PushPlus domain: channels (wechat/mail/cp/webhook), topics and subscribers, friends and blacklists, tokens, messages, preprocessors, forward rules, bots, images, and settings, plus direct send tools. A few minor gaps remain (e.g. no channel add/edit for mail/cp, only list/detail), but core lifecycles are largely represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues