send_textLABSCO SUMMARY
One webhook key, six message shapes, no WeCom app registration.
Because it is the group robot webhook rather than the full WeCom API, setup stops at copying one key out of a URL — and so does the scope: it can post into that one group and upload files, and it cannot read anything. For pushing a result out of an agent run, that is the right size.
What it is
A Go server that sends messages to a WeCom group robot through its webhook, one tool per message type.
What you get
- send_text posts a plain text message to the group
- send_markdown posts formatted markdown
- send_image posts an image
- send_news posts a link card with a title, description, url and picurl
- send_template_card posts a template card message
- upload_file uploads a file to WeCom
Requirements
WECOM_BOT_WEBHOOK_KEY — the key out of the group robot's webhook URL, the part after key=. Install by building from the clone with make build and linking the binary onto your PATH, or take a prebuilt release. No other account or credential.
Setup effort
Add the configuration to your client
USE CASES
01
Pushing the result of a job into the team chat
Send the summary as text or markdown when the run finishes.
02
Sharing a chart or screenshot
Post the image straight into the group instead of saving and re-uploading it.
03
Announcing something with a link
Send a card with a title, description, link and image so it reads as an announcement rather than a URL.
04
Getting a file to the group
Upload it to WeCom from the same conversation you produced it in.
05
Sending a structured notice
Post a template card when a formatted layout carries the message better than plain text.
6 tools
Listed in project docs. Your client may show a different list.
send_markdownsend_imagesend_newssend_template_cardupload_fileBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- mcp-wecombot-server on PATH
- WECOM_BOT_WEBHOOK_KEY in your environment
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
JSON
{
"mcpServers": {
"mcp-wecombot-server": {
"command": "mcp-wecombot-server",
"env": {
"WECOM_BOT_WEBHOOK_KEY": "<YOUR_WECOM_BOT_WEBHOOK_KEY>"
}
}
}
}WECOM_BOT_WEBHOOK_KEY is the key= value at the end of your WeCom group robot's webhook URL (https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=…). The Smithery installer above asks for it and passes it to the server; in a hand-written entry it goes in the env block: "env": {"WECOM_BOT_WEBHOOK_KEY": "<YOUR_WECOM_BOT_WEBHOOK_KEY>"}.
