dingtalk-mcp
Related Servers
Alternatives to dingtalk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables sending messages to Feishu group chats via custom bot webhook, supporting text, rich text, interactive cards, Markdown-converted cards, and chat sharing without requiring an enterprise app.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables posting text messages to Google Chat spaces through webhook-based integration, providing simple and secure message delivery without OAuth setup requirements.MIT
- AlicenseAqualityDmaintenanceIntegrates Claude Code with DingTalk (钉钉) robot notifications, allowing users to send task completion alerts and various message formats to DingTalk groups from Claude Code.540 npm9MIT
- AlicenseNot gradedqualityDmaintenanceEnables posting text messages to Google Chat spaces using webhooks, providing simple integration without OAuth setup required.1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to send DingTalk single and group chat messages via MCP protocol, supporting userId, name, or batch sending to up to 20 users.33MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending text messages, files, and images to Feishu (Lark) group chats via MCP, with support for automatic default group configuration.MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct DingTalk message type (image, text, markdown, news, template card), so the boundaries are clear once the desired format is known. The only mild ambiguity is choosing between markdown/news/template_card for rich content, since all can convey formatted text and links.
All five tools follow the exact same verb_noun convention with a shared `send_` prefix, differing only by message type suffix. This is a fully predictable, uniform pattern.
Five tools is a well-scoped set for a one-way DingTalk messaging integration, each covering one message format. Nothing appears redundant or missing at the count level.
The surface covers all major DingTalk message formats, which is the core of the domain. Minor gaps remain: no file/document sending, no @-mention or recipient targeting parameters, and no webhook/config management or message status/recall operations.