Skip to main content
Glama
MCP Server for notify to weixin / telegram / bark / lark

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

by aahl

💬 Notify MCP Server

简体中文 | English

提供消息推送的 MCP (Model Context Protocol) 服务器,支持企业微信、钉钉、Telegram、Bark、Lark、飞书、Home Assistant

安装

方式1: uvx

{
  "mcpServers": {
    "mcp-notify": {
      "command": "uvx",
      "args": ["mcp-notify"],
      "env": {
        "WEWORK_BOT_KEY": "your-wework-bot-key"
      }
    }
  }
}

方式2: Smithery

需要通过OAuth授权或Smithery key

{
  "mcpServers": {
    "mcp-aktools": {
      "url": "https://server.smithery.ai/@aahl/mcp-notify/mcp" # 流式传输HTTP
    }
  }
}

方式3: Docker

mkdir /opt/mcp-notify
cd /opt/mcp-notify
wget https://raw.githubusercontent.com/aahl/mcp-notify/refs/heads/main/docker-compose.yml
docker-compose up -d
{
  "mcpServers": {
    "mcp-notify": {
      "url": "http://0.0.0.0:8809/mcp" # 流式传输HTTP
    }
  }
}

快速开始

  • 在线体验: fastmcp.cloud

  • 在线体验:

  • 添加到 Cursor Install MCP Server

  • 添加到 VS Code Install MCP Server

  • 添加到 Cherry Studio Install MCP Server

  • 添加到 Claude Code, 执行命令: claude mcp add notify -- uvx mcp-notify

  • 添加到 OpenAI CodeX, 执行命令: codex mcp add notify -- uvx mcp-notify

⚙️ 环境变量

企业微信群机器人

  • WEWORK_BOT_KEY: 企业微信群机器人默认key,也可以在提示词指定

企业微信应用号

  • WEWORK_APP_CORPID: 企业微信所属的企业ID

  • WEWORK_APP_SECRET: 企业微信应用的凭证密钥

  • WEWORK_APP_AGENTID: 企业微信应用的ID,默认: 1000002

  • WEWORK_APP_TOUSER: 企业微信默认接收人ID,也可以在提示词指定,默认: @all

  • WEWORK_BASE_URL: 企业微信API反代理地址,用于可信IP,默认: https://qyapi.weixin.qq.com

钉钉群机器人

  • DINGTALK_BOT_KEY: 钉钉群机器人access_token

  • DINGTALK_BASE_URL: 钉钉API地址,默认: https://oapi.dingtalk.com

飞书/Lark群机器人

  • FEISHU_BOT_KEY: 飞书群机器人key,也可以在提示词指定

  • FEISHU_BASE_URL: 飞书API地址,默认: https://open.feishu.cn

  • LARK_BOT_KEY: Lark群机器人key,也可以在提示词指定

  • LARK_BASE_URL: Lark API地址,默认: https://open.larksuite.com

Telegram

  • TELEGRAM_DEFAULT_CHAT: Telegram 默认会话ID,也可以在提示词指定

  • TELEGRAM_BOT_TOKEN: Telegram 机器人令牌

  • TELEGRAM_BASE_URL: Telegram API反代理地址,默认: https://api.telegram.org

Home Assistant

  • HASS_BASE_URL: Home Assistant 地址,默认: http://homeassistant.local:8123

  • HASS_ACCESS_TOKEN: Home Assistant 长效令牌

  • HASS_MOBILE_KEY: Home Assistant 移动设备key (如: mobile_app_your_iphone),也可在提示词指定

其他

  • BARK_DEVICE_KEY: 默认Bark设备key,也可以在提示词指定

  • BARK_BASE_URL: Bark API地址,默认: https://api.day.app

  • NTFY_DEFAULT_TOPIC: 默认Ntfy订阅主题,也可以在提示词指定

  • NTFY_BASE_URL: Ntfy API地址,默认: https://ntfy.sh

  • PUSH_PLUS_TOKEN: 默认PushPlus令牌,也可以在提示词指定

  • PUSH_PLUS_BASE_URL: PushPlus API地址,默认: http://www.pushplus.plus


Related MCP server: ntfy-mcp

🛠️ 可用工具

  • wework_send_text - 发送文本或Markdown消息

  • wework_send_image - 发送图片消息

  • wework_send_news - 发送图文链接消息

  • wework_app_send_text - 发送文本或Markdown消息

  • wework_app_send_image - 发送图片消息

  • wework_app_send_video - 发送视频消息

  • wework_app_send_voice - 发送语音消息

  • wework_app_send_file - 发送文件消息

  • wework_app_send_news - 发送图文链接消息

  • tg_send_message - 发送文本或Markdown消息

  • tg_send_photo - 发送图片消息

  • tg_send_video - 发送视频消息

  • tg_send_audio - 发送音频消息

  • tg_send_file - 发送文件消息

  • ding_send_text - 通过钉钉群机器人发送文本或Markdown消息

  • lark_send_text - 通过飞书/Lark群机器人发送文本或Markdown消息

  • bark_send_notify - 通过Bark发送通知

  • ntfy_send_notify - 通过Ntfy发送通知

  • pushplus_send_msg - 通过PushPlus发送消息

  • ha_send_mobile - 通过Home Assistant发送通知

  • text_to_sound - 将一段文本转成mp3音频链接


🔗 相关连接


Available Tools

21 tools
bark_send_notifyBark推送通知C

通过Bark推送通知

Inputs: body (required), title, subtitle, device_key, +4 more.

ding_send_text钉钉群机器人-发送文本消息B

钉钉群机器人发送文本或Markdown消息

Inputs: text (required), title, msgtype, bot_key.

ha_send_mobileSend to HomeAssistant Mobile APPC

Send a notification to Home Assistant Mobile APP

Inputs: message (required), title, subtitle, data, +2 more.

lark_send_text飞书/Lark机器人-发送文本消息A

飞书/Lark群机器人发送文本或Markdown消息

Inputs: text (required), msgtype, bot_key, is_lark.

ntfy_send_notifyNtfy Push NotificationC

Push a notification via Ntfy

Inputs: message (required), title, topic, click, +7 more.

pushplus_send_msgPushPlus推送消息C

通过PushPlus(推送加)推送消息

Inputs: content (required), title, token, template, +1 more.

text_to_sound文本转音频B

将一段文本转成mp3音频链接

Inputs: text (required), lang, speed.

tg_send_audioTelegram send audioC

Send audio via telegram bot

Inputs: audio (required), chat_id, caption, parse_mode, +1 more.

tg_send_fileTelegram send fileA

Send general files via telegram bot

Inputs: url (required), chat_id, caption, parse_mode, +1 more.

tg_send_messageTelegram send textB

Send text or markdown message via telegram bot

Inputs: text (required), chat_id, parse_mode, reply_to_message_id.

tg_send_photoTelegram send photoB

Send photo via telegram bot

Inputs: photo (required), chat_id, caption, parse_mode, +1 more.

tg_send_videoTelegram send videoC

Send video via telegram bot

Inputs: video (required), cover, chat_id, caption, +2 more.

wework_app_send_file企业微信应用号-发送文件消息C

通过企业微信应用号发送发送文件消息

Inputs: url (required), touser.

wework_app_send_image企业微信应用号-发送图片消息C

通过企业微信应用号发送发送图片消息

Inputs: url (required), touser.

wework_app_send_news企业微信应用号-发送图文卡片消息C

通过企业微信应用号发送图文卡片消息

Inputs: title (required), url (required), picurl, description, +1 more.

wework_app_send_text企业微信应用号-发送文本消息B

通过企业微信应用号发送文本或Markdown消息

Inputs: text (required), msgtype, touser.

wework_app_send_video企业微信应用号-发送视频消息C

通过企业微信应用号发送发送视频消息

Inputs: url (required), touser.

wework_app_send_voice企业微信应用号-发送语音消息C

通过企业微信应用号发送发送语音消息

Inputs: url (required), touser.

wework_send_image企业微信群机器人-发送图片消息C

通过企业微信群机器人发送图片消息

Inputs: url (required), bot_key.

wework_send_news企业微信群机器人-发送图文消息A

通过企业微信群机器人发送图文链接消息

Inputs: title (required), url (required), picurl, description, +1 more.

wework_send_text企业微信群机器人-发送文本消息C

通过企业微信群机器人发送文本或Markdown消息

Inputs: text (required), msgtype, bot_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers