Skip to main content
Glama
pyang2045

MCP-Pushover Bridge

by pyang2045
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP-Pushover Bridge

No user-submitted related servers found.

    Related Servers

    • PushPlus MCP Server by pushplus

      PushPlus MCP Serverofficial

      pushplus
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to send push notifications to WeChat, email, and other channels via PushPlus, supporting multiple message formats and channels.
      100
      19 npm
      3
      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
      2 npm
      MIT

    • ntfy MCP Server

      hexerei
      A
      license
      Not graded
      quality
      C
      maintenance
      Send push notifications to mobile devices via ntfy.sh from AI assistants.
      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
      4 npm
      1
      MIT

    • blipr-mcp

      applogico
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to send push alerts to your phone via Blipr, useful for notifying when tasks complete, builds break, or approvals are needed.
      5
      15 npm
      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 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The single tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool name 'pushover_send_message' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.

    Tool Count2/5

    A single tool is too few for a server named 'MCP-Pushover Bridge', which implies a bridge to the Pushover service. While sending messages is a core function, typical notification services might include additional operations like checking message status or managing user settings, making this feel thin and under-scoped.

    Completeness2/5

    The tool surface is severely incomplete for a Pushover bridge. It only covers sending messages, missing obvious operations such as checking message delivery status, retrieving user information, or handling priority settings, which are common in notification APIs and could lead to agent failures in broader workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources