MCP Server for notify to weixin / telegram / bark / lark
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEWORK_BOT_KEY | No | 企业微信群机器人key | |
| WEWORK_BASE_URL | No | 企业微信API反代理地址，用于可信IP | https://qyapi.weixin.qq.com |
| TELEGRAM_BASE_URL | No | Telegram API base URL | https://api.telegram.org |
| WEWORK_APP_CORPID | No | 企业微信所属的企业ID | |
| WEWORK_APP_SECRET | No | 企业微信应用的凭证密钥 | |
| WEWORK_APP_TOUSER | No | 企业微信默认接收人ID | |
| TELEGRAM_BOT_TOKEN | No | Telegram Bot Token | |
| WEWORK_APP_AGENTID | No | 企业微信应用的ID | |
| TELEGRAM_DEFAULT_CHAT | No | Telegram Default Chat ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wework_send_textC | 通过企业微信群机器人发送文本或Markdown消息 |
| wework_send_imageC | 通过企业微信群机器人发送图片消息 |
| wework_send_newsA | 通过企业微信群机器人发送图文链接消息 |
| wework_app_send_textB | 通过企业微信应用号发送文本或Markdown消息 |
| wework_app_send_imageC | 通过企业微信应用号发送发送图片消息 |
| wework_app_send_videoC | 通过企业微信应用号发送发送视频消息 |
| wework_app_send_voiceC | 通过企业微信应用号发送发送语音消息 |
| wework_app_send_fileC | 通过企业微信应用号发送发送文件消息 |
| wework_app_send_newsC | 通过企业微信应用号发送图文卡片消息 |
| tg_send_messageB | Send text or markdown message via telegram bot |
| tg_send_photoB | Send photo via telegram bot |
| tg_send_videoC | Send video via telegram bot |
| tg_send_audioC | Send audio via telegram bot |
| tg_send_fileA | Send general files via telegram bot |
| ding_send_textB | 钉钉群机器人发送文本或Markdown消息 |
| lark_send_textA | 飞书/Lark群机器人发送文本或Markdown消息 |
| bark_send_notifyC | 通过Bark推送通知 |
| ntfy_send_notifyC | Push a notification via Ntfy |
| pushplus_send_msgC | 通过PushPlus(推送加)推送消息 |
| ha_send_mobileC | Send a notification to Home Assistant Mobile APP |
| text_to_soundB | 将一段文本转成mp3音频链接 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
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.
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).
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.
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.