Skip to main content
Glama
aahl

MCP Server for notify to weixin / telegram / bark / lark

by aahl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to MCP Server for notify to weixin / telegram / bark / lark

Related Servers

  • ntfy-mcp

    teddyzxcv
    A
    license
    Not graded
    quality
    D
    maintenance
    The MCP server that keeps you informed by sending the notification on phone using ntfy.sh
    327 npm
    45
    Apache 2.0

  • ntfy-mcp

    Edqe14
    A
    license
    C
    quality
    D
    maintenance
    MCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.
    2
    7 npm
    MIT

  • mcp-gotify

    fastmcp-me
    A
    license
    B
    quality
    D
    maintenance
    MCP server for sending Gotify push notifications to your devices.
    1
    MIT

  • EdgeOne MCP Pusher

    ersanpt
    A
    license
    Not graded
    quality
    C
    maintenance
    Free self-hosted WeChat push notification service with a standard MCP Server, enabling message sending via Webhook or MCP tools.
    GPL 3.0
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 21 tools

Disambiguation5/5

Each tool is uniquely identified by its platform prefix and action, making it easy for an agent to distinguish between sending text via Telegram vs. WeWork. There is no overlap in purpose.

Naming Consistency4/5

Most tools follow a consistent 'platform_verb_object' pattern (e.g., tg_send_message, wework_send_text). The exceptions are 'text_to_sound' (no platform prefix and a different verb structure) and 'ha_send_mobile' (missing underscore).

Tool Count4/5

With 21 tools across 9 platforms, the count is high but justified by the variety of platforms and message types. Each tool serves a distinct purpose, though some platforms have only a single tool.

Completeness4/5

The server covers a broad range of notification platforms with essential message types (text, image, file, etc.). Minor gaps exist (e.g., no Telegram location or email), and 'text_to_sound' seems tangential, but core notification workflows are well-supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources