- Home
- MCP servers
- MCP Wecombot Server
MCP Wecombot Server
- javascript
33
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"gotoolkits-mcp-wecombot-server": {
"command": "mcp-wecombot-server",
"args": [],
"env": {
"WECOM_BOT_WEBHOOK_KEY": "YOUR_WEBHOOK_KEY"
}
}
}
}You run an MCP server that delivers various WeCom group messages by connecting to a WeCom robot webhook. This server lets you send text, markdown, images, and news cards to your WeCom group from MCP clients and prompts you to configure a webhook key for authentication.
How to use
You connect an MCP client to the WeCom bot server to send messages to your WeCom group. You can trigger different message types such as text, markdown, images, and news cards from your MCP prompts. Start by ensuring your webhook key is configured so the server can authenticate with the WeCom group robot. Then issue the appropriate command from your MCP client to request the specific message type you want to send.
How to install
Prerequisites you need before installation: Node.js and npm, Git, and build tools if you plan to build from source.
# Install via automated tool (preferred for Claude Desktop users)
npx -y @smithery/cli install @gotoolkits/mcp-wecombot-server --client claude-desktop
# Manual installation from source
# 1) Clone the repository and build
git clone https://github.com/gotoolkits/mcp-wecombot-server.git
cd mcp-wecombot-server
make build
# 2) Create a symlink to the binary in /usr/local/bin
sudo ln -s $PWD/dist/mcp-wecombot-server_xxx_xxxx /usr/local/bin/mcp-wecombot-server
# Note: "$PWD/dist/mcp-wecombot-server_xxx_xxxx" should be replaced with the actual binary file name
# You can also download and use the pre-compiled release binary package.
````]} ,{
Configuration details are provided below. Create a configuration that defines how the MCP server runs and what environment variables it requires. A sample configuration is shown in the next section.
Additional content
Configuration and environment variables enable the server to connect to the WeCom group robot port. The sample configuration below shows how to run the server locally with an environment variable for the webhook key.
{
"mcpServers": {
"mcp-wecombot-server": {
"command": "mcp-wecombot-server",
"env": {
"WECOM_BOT_WEBHOOK_KEY": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx"
}
}
}
}
````}]}] },
WeCom Robot configuration notes: you will use a webhook URL that includes your unique WECOM_BOT_WEBHOOK_KEY. The required key appears in your WeCom webhook URL as the value after key=, and you must keep this value secret to protect access to your WeCom group.
Tools and endpoints
This MCP server exposes a set of actions you can invoke from an MCP client to deliver different types of WeCom messages.
Available tools
send_text
Sends a text message to the WeCom group with specified content.
send_markdown
Sends a Markdown-formatted message to the WeCom group.
send_image
Sends an image message to the WeCom group using a provided image URL.
send_news
Sends a News card consisting of a title, description, URL, and image to the WeCom group.
send_template_card
Sends a template card message to the WeCom group for richer content and layout.
upload_file
Uploads a file to WeCom for distribution through the group robot.