Skip to content
MCP Server Directory logo
communication-collaboration

Mcp Dingdingbot Server

钉钉webhook MCP server

Reviewed overview

MCP サーバー概要

What is the project about? Mcp Dingdingbot Server is an MCP (Message Control Protocol) server that sends various message types to DingDing (钉钉) group robots. It supports text, Markdown, image, news (graphic), template card messages and file uploads, with optional HMAC-SHA256 signature verification for enhanced security.

How to use the project?

  1. Install: git clone https://github.com/HundunOnline/mcp-dingdingbot-server.git && make build, or download the precompiled release binary.
  2. Configure: set environment variables in your MCP config: DINGDING_BOT_WEBHOOK_KEY (required) and DINGDING_BOT_SIGN_KEY (optional).
  3. Deploy/run the binary (mcp-dingdingbot-server) or register it in your MCP server list.
  4. Use the provided commands/endpoints to send messages: send_text, send_markdown, send_image, send_news, send_template_card, upload_file. Examples and sample prompts are in the README.
  5. Refer to DingTalk robot docs for webhook and signature setup: https://open.dingtalk.com/document/robots/custom-robot-access

Key features:

  • Send text, Markdown, image, news (title/desc/url/pic), and template card messages
  • File upload support to DingDing
  • Signature verification (HMAC-SHA256) for secure requests
  • Simple deployment as a standalone binary or MCP service
  • Configurable via environment variables
  • Sample prompts and usage examples provided in README

Use cases:

  1. Team notifications and announcements to DingDing groups
  2. CI/CD and monitoring alerts forwarded to group robots
  3. Automated reports and summaries delivered to project channels
  4. Sharing images, news links, or files with teams
  5. Integrating internal systems or scripts with DingDing via MCP

FAQ from the project:

  • Q: Which environment variables are required? A: DINGDING_BOT_WEBHOOK_KEY is required. DINGDING_BOT_SIGN_KEY is optional but recommended when robot security is enabled.
  • Q: How is request signing done? A: Using HMAC-SHA256 with timestamp and the sign key as described in DingTalk docs.
  • Q: What message types are supported? A: Text, Markdown, Image, News (link+image), Template Card, and file uploads.
  • Q: How do I install and run it? A: Build from source with make build or download the release binary, then place the binary in PATH and run or configure it in your MCP servers list.
  • Q: Where to get the webhook and sign key? A: Create/configure a custom robot in DingTalk and copy the access_token (webhook key) and optional signature secret from the robot security settings.
  • Q: Are there examples? A: Yes — the README includes sample prompts and usage examples for different message types.