home / mcp / dingdingbot mcp server

DingDingbot MCP Server

钉钉webhook MCP server

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "hundunonline-mcp-dingdingbot-server": {
      "command": "mcp-dingdingbot-server",
      "args": [],
      "env": {
        "DINGDING_BOT_SIGN_KEY": "SECxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "DINGDING_BOT_WEBHOOK_KEY": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx"
      }
    }
  }
}

This MCP server lets you send a variety of DingDing group messages from a centralized server. You configure a DingDing bot webhook and an optional signature key, then issue MCP commands to deliver text, markdown, image, news, or template card messages, and upload files to the group robot. This enables automated alerts, status updates, and rich communications in your DingDing groups.

How to use

You run an MCP client that connects to this server to send messages to your DingDing group robot. Typical usage involves starting the server with your DingDing webhook settings, then issuing commands like send_text, send_markdown, send_image, send_news, send_template_card, or upload_file through your MCP client. Each command tells the server which message type to deliver and to which group robot to post it.

How to install

# prerequisites
# - Git is installed
# - make is installed (for building the server)

# clone the repository and build
$ git clone https://github.com/HundunOnline/mcp-dingdingbot-server.git
$ cd mcp-dingdingbot-server && make build
$ sudo ln -s $PWD/dist/mcp-dingdingbot-server_xxx_xxxx /usr/local/bin/mcp-dingdingbot-server

# "$PWD/dist/mcp-dingdingbot-server_xxx_xxxx" should be replaced with the actual binary name

# You can also download and use a pre-compiled release binary package if you prefer

Additional configuration and usage notes

Configure the MCP server with environment variables that specify how to reach the DingDing bot and how to verify requests. The following example shows the required and optional variables. You will place these in the MCP server configuration so the server starts with the correct settings.

{
  "mcpServers": {
    "mcp-dingdingbot-server": {
      "command": "mcp-dingdingbot-server",
      "env": {
        "DINGDING_BOT_WEBHOOK_KEY": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx",
        "DINGDING_BOT_SIGN_KEY": "SECxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Usage patterns and capabilities

The server supports multiple message types so you can automate alerts and rich messages to your DingDing group. Message types include text, markdown, image, and news entries. You can also send template cards or upload files to DingDing through your MCP client. If you enable signature verification, requests are authenticated using the configured sign key and a timestamp.

Security notes

Optionally enable signature verification for enhanced security. When enabled, the server uses HMAC-SHA256 to verify requests against the provided sign key combined with a timestamp.

Available tools

send_text

Send a text message to the DingDing group robot.

send_markdown

Send a Markdown-formatted message to the DingDing group robot.

send_image

Send an image message to the DingDing group robot.

send_news

Send a news message to the DingDing group robot, including title, description, URL, and image URL.

send_template_card

Send a template card message to the DingDing group robot.

upload_file

Upload a file to the DingDing group robot.