MCP SERVERPost to a WeCom (WeChat Work) group from an assistant — markdown with @mentions, images, files and template cards — routed to whichever bot you name.
LABSCO SUMMARY
The multi-bot setup is what makes this more than a single-channel poster: configure an alert bot and a CI bot, and a send can name which one delivers, so notifications land in the right group without separate integrations. The @mention handling is the other convenience — it translates 'notify Alice' into the <@alice> syntax WeCom actually needs rather than leaving you to format it.
A Python server for WeCom bot webhooks: six tools that send messages, images, files and template cards to a WeChat Work group, with routing across several configured bots.
A WeCom group bot webhook URL, of the form https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=..., set as WECOM_WEBHOOK_URL for a single default bot. For several bots, set WECOM_BOTS as a JSON map of bot_id to name, webhook_url and description, or one WECOM_BOT_<NAME>_URL variable per bot. Python, run from the wecom-bot-mcp-server package as its console script.
Add the configuration to your client
USE CASES
Discover which bots are configured, then post a formatted markdown update to the CI or alert group, mentioning whoever needs to act on it.
Send a report or an image straight to a WeCom group from a local path, routed to the bot that serves that channel.
Send a template card — a text notice or a news notice — when a plain message is not enough and the update needs WeCom's card layout.
Turn 'remind these two people' into a markdown message carrying their <@userid> mentions, so the notification actually pings them in the group.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_wecom_botsList all configured WeCom bots.
Use this tool to discover available bots before sending messages. Each bot has an id, name, and optional description.
Returns: dict: Contains 'bots' list and 'count' of available bots. Each bot entry has: id, name, description, has_webhook
send_messagePost a text or markdown message to a WeCom group. People are notified by putting <@userid> or <@all> in the content, or through mentioned_list and mentioned_mobile_list.
send_wecom_fileSend file to WeCom.
Args: file_path: Path to the file to send bot_id: Bot identifier for multi-bot setups. If None, uses the default bot.
Returns: dict: Response with file information and status
Raises: WeComError: If file sending fails
send_wecom_imageSend image to WeCom.
Args: image_path: Path to the image file to send bot_id: Bot identifier for multi-bot setups. If None, uses the default bot.
Returns: dict: Response with image information and status
Raises: WeComError: If image sending fails
send_wecom_template_card_news_noticeMCP tool wrapper for sending a news_notice template card.
send_wecom_template_card_text_noticeMCP tool wrapper for sending a text_notice template card.
The structure of the template card fields follows the WeCom template_card documentation and notify-bridge examples.
BEFORE YOU INSTALL
6 tools when we connected.
All 6 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
{
"mcpServers": {
"wecom": {
"command": "uvx",
"args": [
"wecom-bot-mcp-server"
],
"env": {
"WECOM_WEBHOOK_URL": "<YOUR_WECOM_WEBHOOK_URL>"
}
}
}
}{
"mcpServers": {
"wecom": {
"command": "uvx",
"args": [
"wecom-bot-mcp-server"
],
"env": {
"WECOM_WEBHOOK_URL": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=<YOUR_KEY>"
}
}
}
}{
"servers": {
"wecom": {
"command": "uvx",
"args": [
"wecom-bot-mcp-server"
],
"env": {
"WECOM_WEBHOOK_URL": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=<YOUR_KEY>"
}
}
}
}MCP servers
gotoolkits
shellus
SilasReinagel
Songmengdi