Notify MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 258 installs a week from pypi. Last commit 26 Mar 2026.
MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk
We read the source, 21 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
TELEGRAM_BASE_URL = os.getenv("TELEGRAM_BASE_URL") or "https://api.telegram.org"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-notify -- uvx mcp-notify
{
"mcpServers": {
"mcp-notify": {
"args": [
"mcp-notify"
],
"command": "uvx"
}
}
}
[mcp_servers.mcp-notify]
command = "uvx"
args = ["mcp-notify"]
{
"mcpServers": {
"mcp-notify": {
"args": [
"mcp-notify"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"mcp-notify": {
"args": [
"mcp-notify"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
WEWORK_BOT_KEY (The default key for the WeWork group robot can also be specified in the prompt), WEWORK_APP_CORPID (Company ID of WeWork), WEWORK_APP_SECRET (Secret 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 (Access token of DingTalk Robot, Can also be specified in the prompt), LARK_BOT_KEY (The key of Lark Robot, Can also be specified in the prompt), FEISHU_BOT_KEY (The 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 (Telegram Bot Token), PUSH_PLUS_TOKEN (Default PushPlus token, Can also be specified in the prompt).
The author declared them in the registry entry; get the values from the project itself.
Multi-channel messaging MCP server for Slack, Telegram, Email, KakaoTalk, and Discord.
MCP server that exposes a Telegram bot
MCP server for aiogram Telegram bots — 30 tools, 7 resources, 3 prompts, event streaming
MCP server for Telegram Archive — search messages, browse chats, and access history
MCP server for controlling Discord servers via bot token
Local-first MCP server for your own LINE and Telegram chats. Data stays on your machine.
MCP server for Marketo — 32 tools for leads, programs, emails, forms, lists, and bulk export.
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
Answers built from our own checks of this server.