mcp-dingdingbot

This MCP server, mcp-dingdingbot-server, enables you to send a variety of DingDing group messages through a DingDing group robot. It supports text, markdown, image, news, and template card messages, as well as file uploads. You can manage access securely via signature verification if you enable the DINGDING_BOT_SIGN_KEY. Use the provided commands to construct and dispatch messages to your DingDing group robot.

Once the server is running and configured with your DingDing webhook and (optionally) a signature key, you can invoke its built-in capabilities such as send_text, send_markdown, send_image, send_news, send_template_card, and upload_file to interact with the DingDing group robot.

Prerequisites:

• Git
• Go tooling and Makefile support (for building the binary via make build)
• Access to the repository https://github.com/HundunOnline/mcp-dingdingbot-server

Steps:

1. Clone the repository:

git clone https://github.com/HundunOnline/mcp-dingdingbot-server.git

2. Change into the project directory and build:

cd mcp-dingdingbot-server
make build

3. Optional: create a symlink to make the binary easily runnable from anywhere (adjust the binary name if needed):

sudo ln -s $PWD/dist/mcp-dingdingbot-server_xxx_xxxx /usr/local/bin/mcp-dingdingbot-server

Replace "$PWD/dist/mcp-dingdingbot-server_xxx_xxxx" with the actual produced binary name. 4) Prepare configuration via mcp_config format (see README example) and start the server with the required environment variables:

# Example environment setup (adjust keys accordingly)
export DINGDING_BOT_WEBHOOK_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
export DINGDING_BOT_SIGN_KEY=SECxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

# Run the server (adjust path if needed)
mcp-dingdingbot-server

5. Alternatively, download and use a pre-compiled release binary package if available and place it in your PATH.

Notes and tips:

• The server requires DINGDING_BOT_WEBHOOK_KEY to be set. This is the webhook token for your DingDing group robot and is mandatory for forwarding messages.
• DINGDING_BOT_SIGN_KEY is optional but recommended when you want signature verification for enhanced security. If enabled, requests must be signed using HMAC-SHA256 with the provided timestamp and secret key.
• Ensure network access from the server to the DingDing webhook endpoint is allowed (no outbound blocks).
• The configuration format follows the MCP standard shown in the README, with the mcpServers map containing the server entry and its environment variables.
• If you modify env vars, restart the MCP server to apply changes.
• The server supports uploading files to DingDing via upload_file in addition to sending various message types.