mcp-dingding-bot
mcp-dingding-bot is an MCP server. It reaches dingtalk. It needs DINGTALK_BOT_ACCESS_TOKEN and DINGTALK_BOT_SECRET to authenticate. Its repository has 12 GitHub stars and is licensed under MIT; we last read it on 2026-10-23.
Sends text or markdown messages via Dingding (DingTalk) group custom robot from an MCP server.
Install
MCP servers are packaged differently from each other -- some run via npx, some as a Docker image, some as a plain script you clone and run. mcp-dingding-bot’s own README did not state one plainly enough for this page to quote it rather than guess, so it will not guess. The repository below states it.
What it reaches, and what it needs
Reaches
dingtalk
Credential
DINGTALK_BOT_ACCESS_TOKEN, DINGTALK_BOT_SECRET
Maintenance
Stars
12
State
stale
Licence
MIT
From the repository
MCP Server for send text/markdown message via dingding (aka dingtalk) group custom robot
Common questions about mcp-dingding-bot
- What does mcp-dingding-bot do?
- Sends text or markdown messages via Dingding (DingTalk) group custom robot from an MCP server.
- How do I install mcp-dingding-bot?
- Its README did not state an install command plainly enough for us to quote one, so we do not guess. The repository has the instructions: https://github.com/Shawyeok/mcp-dingding-bot
- What does mcp-dingding-bot connect to, and what does it need?
- It reaches dingtalk. The credentials we found in its source are DINGTALK_BOT_ACCESS_TOKEN and DINGTALK_BOT_SECRET.
- Is mcp-dingding-bot official and is it maintained?
- We found nothing naming it as a vendor’s official server. Its repository has 12 GitHub stars and its state in our directory is stale. Its last commit we recorded was on 2025-07-08.
- What licence does mcp-dingding-bot use?
- The repository declares the MIT licence.