A Model Context Protocol (MCP) compliant server implementation for WeCom (WeChat Work) bot.
A Model Context Protocol (MCP) compliant server implementation for WeCom (WeChat Work) bot. Exposed over MCP by the wecom bot mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
Parameters — content, msg_type (markdown/markdown_v2), mentioned_list, mentioned_mobile_list, bot_idmarkdown — Use when content contains @userid mentions or font colors. The @userid syntax is WeCom's official mention format, which avoids conflicts withmarkdown_v2 — Use for tables, lists, embedded images, or general content (default)Returns — List of available bots with their IDs, names, and descriptionsTesting — The Testing tool exposed by this serverYou will need 5 environment variables: WECOM_WEBHOOK_URL, WECOM_BOTS, WECOM_BOT_ALERT_URL, WECOM_BOT_CI_URL, WECOM_BOT_NOTIFY_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wecom Bot's toolset — Parameters, markdown, markdown_v2 and 2 more — is a fair guide to whether it matches your workflow. It is maintained by loonghao; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Parameters | content, msg_type (markdown/markdown_v2), mentioned_list, mentioned_mobile_list, bot_id |
| markdown | Use when content contains <@userid> mentions or font colors. The <@userid> syntax is WeCom's official mention format, which avoids conflicts with email addresses like @user@email.com |
| markdown_v2 | Use for tables, lists, embedded images, or general content (default) |
| Returns | List of available bots with their IDs, names, and descriptions |
| Testing | The Testing tool exposed by this server. |
{
"mcpServers": {
"wecom": {
"command": "uvx",
"args": ["wecom-bot-mcp-server"],
"env": {
"WECOM_WEBHOOK_URL": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=default",
"WECOM_BOTS": "{\"alert\": {\"name\": \"Alert Bot\", \"webhook_url\": \"https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=alert\"}, \"ci\": {\"name\": \"CI Bot\", \"webhook_url\": \"https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=ci\"}}"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WECOM_WEBHOOK_URL | Endpoint or connection string the server talks to. | Yes |
| WECOM_BOTS | Configuration value read at startup. | Optional |
| WECOM_BOT_ALERT_URL | Endpoint or connection string the server talks to. | Yes |
| WECOM_BOT_CI_URL | Endpoint or connection string the server talks to. | Yes |
| WECOM_BOT_NOTIFY_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.