The mcp-wecombot-server is an MCP server that forwards messages to a WeCom (WeChat Work) group robot. It exposes tools to send text, markdown, image, news, and template card messages, as well as upload files to the WeCom group robot for broadcasting in your workspace. To use it, configure the server with your WeCom webhook key and run the server in your preferred environment. Once running, you can invoke the available actions (send_text, send_markdown, send_image, send_news, send_template_card, upload_file) via the MCP protocol to deliver content to the designated WeCom group via the robot webhook.

Typical workflow:

• Set WECOM_BOT_WEBHOOK_KEY in the environment to your WeCom robot webhook key.
• Start the MCP server using your chosen runtime (as configured).
• Use the provided actions to send messages; for example, send_text to post plain text, or send_image to post an image message with a URL. Each action corresponds to a specific payload format understood by the WeCom webhook.

The server is especially suitable for automation pipelines, chatops, or tools that need to broadcast information into a WeCom group without manual UI steps.

Prerequisites:

• A running MCP runtime and environment (Node, Python, or binary environment compatible with MCP server format).
• A WeCom group robot webhook key (WECOM_BOT_WEBHOOK_KEY) from the WeCom admin console.

Manual installation steps:

1. Clone the repository and build (if needed): git clone https://github.com/gotoolkits/mcp-wecombot-server.git cd mcp-wecombot-server make build

2. Install the server binary globally (if the project provides a prebuilt binary): sudo ln -s $PWD/dist/mcp-wecombot-server_xxx_xxxx /usr/local/bin/mcp-wecombot-server

   Replace the binary name with the actual generated file name

3. Provide configuration for the MCP server: Create or edit the configuration file (as shown in the README example), and set the environment variable: WECOM_BOT_WEBHOOK_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx

4. Run the server:

   • If using the provided config, start the server process (for example): mcp-wecombot-server
   • Ensure the environment variable is available to the process (export WECOM_BOT_WEBHOOK_KEY=... if launching from a shell).

5. Optional: Use Smithery or your preferred deployment method to integrate and manage the MCP server in your environment.

Tips and notes:

• Ensure the WECOM_BOT_WEBHOOK_KEY is kept secret; do not commit it to source control.
• The server supports multiple message types; construct the payloads per the action (send_text, send_markdown, send_image, send_news, send_template_card, upload_file) to match the WeCom API expectations.
• If you update the webhook key, restart the MCP server so it picks up the new value.
• When running via Smithery or containerized environments, map the WECOM_BOT_WEBHOOK_KEY as an environment variable inside the container or deployment manifest.
• Review WeCom webhook rate limits and payload size limits to avoid message drops.
• For image and news messages, provide correctly structured content with URLs and, if required, authentication headers via the webhook key.
• Debug by sending a simple text message first to confirm connectivity before attempting rich content payloads.