mcp-dingding-bot
[](https://mseep.ai/app/shawyeok-mcp-dingding-bot)
# MCP DingDing Bot
MCP Server for the DingDing Bot API, enabling DingDing / Dingtalk message notifications and interactions.
## Features
* **Message Notifications**: Send various types of DingDing messages (text / markdown)
## Tools
1. `send_text_message`
* Send a plain text message to a dingding group
* Inputs:
* `text` (string): Text content
* `atAll` (optional boolean): Whether to @ all members
2. `send_markdown_message`
* Send a markdown formatted message to a dingding group
* Inputs:
* `title` (string): Message title
* `text` (string): Markdown content
* `atAll` (optional boolean): Whether to @ all members
## Setup
### DingDing Bot Token
1. Create a DingDing group chat bot:
* Go to group settings > Group Bot Management
* Create a custom bot
* Save the webhook URL and secret
### Usage with Claude Desktop
Add the following to your `claude_desktop_config.json`:
### Docker
```json
{
"mcpServers": {
"gitlab": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"DINGTALK_BOT_ACCESS_TOKEN",
"-e",
"DINGTALK_BOT_SECRET",
"shawyeok/mcp-dingding-bot"
],
"env": {
"DINGTALK_BOT_ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
"DINGTALK_BOT_SECRET": "<YOUR_SECRET>" // Optional, for robots with signature verification enabled
}
}
}
}
```
### NPX
```json
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": [
"-y",
"mcp-dingding-bot"
],
"env": {
"DINGTALK_BOT_ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
"DINGTALK_BOT_SECRET": "<YOUR_SECRET>" // Optional, for robots with signature verification enabled
}
}
}
}
```
## Build
Docker build:
```shell
docker build -t shawyeok/mcp-dingding-bot .
```
## Environment Variables
- `DINGTALK_BOT_ACCESS_TOKEN`: Your dingding group robot access token (required)
- `DINGTALK_BOT_SECRET`: Your dingding group robot signature secret (optional)
## References
- https://modelcontextprotocol.io/quickstart/server
- https://open.dingtalk.com/document/robots/custom-robot-access
## License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one sends markdown-formatted messages, and the other sends plain text messages. While both involve sending messages, the format distinction is explicit and unlikely to cause confusion, though they could be seen as overlapping in the broader 'send message' function.
Both tool names follow a consistent verb_noun pattern with 'send_' prefix and descriptive suffixes ('markdown_message', 'text_message'). The naming is predictable and adheres to a clear convention throughout the set.
With only 2 tools, the server feels thin for a bot that might handle more messaging operations (e.g., sending images, files, or managing conversations). This minimal set limits functionality and suggests an incomplete surface for a typical bot domain.
The tool set is severely incomplete for a Dingding bot domain. It only covers sending two message types, missing essential operations like receiving messages, managing users or groups, handling events, or supporting other media formats, which will likely cause agent failures in broader use cases.