mcp-dingding-bot

This MCP server enables sending DingTalk (DingDing) messages to groups via a bot. It exposes two tools: send_text_message and send_markdown_message. Use send_text_message to deliver plain text to a DingTalk group, with an optional atAll flag to mention everyone. Use send_markdown_message to post rich markdown content, including a title and markdown body, also with an optional atAll flag. To operate the bot, you must provide DingTalk credentials: a group bot access token and, if your bot signature verification is enabled, a secret. Configure these via environment variables (DINGTALK_BOT_ACCESS_TOKEN and DINGTALK_BOT_SECRET) depending on your deployment method. Example usage through the MCP server captures the inputs for text or markdown content and forwards them to the DingTalk API using the bot configured by your token/secret.

Prerequisites:

• Docker or Node.js environment (if using NPX) or a system capable of running NPX/Docker commands
• Access to a DingTalk group bot, with token and optional secret

Installation steps (Docker):

1. Ensure Docker is installed and running.
2. Run the MCP server using the provided environment variables: docker run --rm -i
   -e DINGTALK_BOT_ACCESS_TOKEN=YOUR_TOKEN
   -e DINGTALK_BOT_SECRET=YOUR_SECRET
   shawyeok/mcp-dingding-bot

Installation steps (NPX):

1. Ensure Node.js and npm are installed.
2. Install and start via NPX with required env vars: npx -y mcp-dingding-bot (Or set env vars in your shell before running the command)
3. If you need to pass the secret, set DINGTALK_BOT_SECRET accordingly.

Notes:

• The DOCKER example uses the official shawyeok/mcp-dingding-bot image.
• The NPX example pulls the package on-demand, which may be convenient for quick tests.

Environment variables:

• DINGTALK_BOT_ACCESS_TOKEN: Required. The DingTalk group robot access token.
• DINGTALK_BOT_SECRET: Optional. The secret for signature verification (needed for robots with verification enabled). Common issues:
• Ensure the token is valid and has permission to post in the target group.
• If using the secret, verify that the DingTalk bot is configured to require a signature.
• When using NPX, network access is required to fetch the package at startup. Configuration tips:
• You can run multiple MCP servers in parallel by adding more entries under mcpServers with distinct names (e.g., dingding-docker, dingding-npx).
• For production, prefer the Docker deployment to avoid local Node dependencies and ensure stable runtime.