Model Context Protocol (MCP) server for WeCom Bot message sending
Wecom MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Model Context Protocol (MCP) server for WeCom Bot message sending.
Configuration can be set via CLI flags, environment variables, or a config file.
Installation goes through your MCP client rather than a global install: point it at @futuretea/wecom-bot-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Wecom is connected, these are the calls the assistant has available:
content — stringmentioned_list — string[]mentioned_mobile_list — string[]base64 — stringmd5 — stringarticles — object[]main_title — stringmain_title_desc — stringsub_title — stringsource — objectsource.icon_url — stringsource.desc — stringYou will need 3 environment variables: YOUR_KEY, WECOM_MCP_WECOM_BOT_KEY, WECOM_MCP_WECOM_BOT_API_BASE_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.
https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY)This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wecom's toolset — content, mentioned_list, mentioned_mobile_list and 11 more — is a fair guide to whether it matches your workflow. It is maintained by futuretea; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Wecom's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| content | string |
| mentioned_list | string[] |
| mentioned_mobile_list | string[] |
| base64 | string |
| md5 | string |
| articles | object[] |
| main_title | string |
| main_title_desc | string |
| sub_title | string |
| source | object |
| source.icon_url | string |
| source.desc | string |
| emphasis_content | object |
| emphasis_content.title | string |
{
"mcpServers": {
"wecom-bot-1": {
"command": "npx",
"args": ["-y", "@futuretea/wecom-bot-mcp-server"],
"env": {
"YOUR_KEY": "your-value",
"WECOM_MCP_WECOM_BOT_KEY": "your-value",
"WECOM_MCP_WECOM_BOT_API_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY)| Variable | Description | Required |
|---|---|---|
| YOUR_KEY | Credential the server authenticates with. | Yes |
| WECOM_MCP_WECOM_BOT_KEY | Credential the server authenticates with. | Yes |
| WECOM_MCP_WECOM_BOT_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.