Skip to content
mcp/skillhub

Notify MCP Server

by aahlio.github.aahl/mcp-notifyv0.1.11

MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk

28Pythonstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Stale7mo ago

Install Notify MCP server

Install in Claude Code

claude mcp add notify -e WEWORK_BOT_KEY='<wework-bot-key>' -e WEWORK_APP_SECRET='<wework-app-secret>' -e DINGTALK_BOT_KEY='<dingtalk-bot-key>' -e LARK_BOT_KEY='<lark-bot-key>' -e FEISHU_BOT_KEY='<feishu-bot-key>' -e TELEGRAM_BOT_TOKEN='<telegram-bot-token>' -e PUSH_PLUS_TOKEN='<push-plus-token>' -- uvx mcp-notify

Configuration

VariableRequiredSecretDescription
TRANSPORT——Transport protocol to use
WEWORK_BOT_KEY—yesThe default key for the WeWork group robot can also be specified in the prompt
WEWORK_APP_CORPID——Company ID of WeWork
WEWORK_APP_SECRET—yesSecret key of WeWork
WEWORK_APP_AGENTID——Agent ID of WeWork Application, Default: 1000002
WEWORK_APP_TOUSER——Default recipient user ID in WeWork, Default: @all
DINGTALK_BOT_KEY—yesAccess token of DingTalk Robot, Can also be specified in the prompt
LARK_BOT_KEY—yesThe key of Lark Robot, Can also be specified in the prompt
FEISHU_BOT_KEY—yesThe key of Feishu Robot, Can also be specified in the prompt
TELEGRAM_DEFAULT_CHAT——Telegram Default Chat ID, Can also be specified in the prompt
TELEGRAM_BOT_TOKEN—yesTelegram Bot Token
PUSH_PLUS_TOKEN—yesDefault PushPlus token, Can also be specified in the prompt

Freshness

Stale — last maintenance signal 7mo ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-03-26 · 7mo ago · GitHub

  2. Latest release

    2026-03-26 · 7mo ago · GitHub · 0.1.11

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-03-26 · 7mo ago · official registry · v0.1.11

FAQ

›How do I install the Notify MCP server in Claude Code?

Run: claude mcp add notify -e WEWORK_BOT_KEY='<wework-bot-key>' -e WEWORK_APP_SECRET='<wework-app-secret>' -e DINGTALK_BOT_KEY='<dingtalk-bot-key>' -e LARK_BOT_KEY='<lark-bot-key>' -e FEISHU_BOT_KEY='<feishu-bot-key>' -e TELEGRAM_BOT_TOKEN='<telegram-bot-token>' -e PUSH_PLUS_TOKEN='<push-plus-token>' -- uvx mcp-notify. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Notify require an API key?

Yes. It expects WEWORK_BOT_KEY, WEWORK_APP_SECRET, DINGTALK_BOT_KEY, LARK_BOT_KEY, FEISHU_BOT_KEY, TELEGRAM_BOT_TOKEN, PUSH_PLUS_TOKEN, of which 7 are secrets.

›Can I use Notify as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Notify in the official MCP registry?

Yes, as io.github.aahl/mcp-notify.

Alternatives to Notify

Other communication MCP servers.

View all