dingtalk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DINGTALK_SECRET | No | 钉钉机器人加签密钥(安全设置 → 加签 → SEC 开头的字符串) | |
| DINGTALK_ACCESS_TOKEN | Yes | 钉钉机器人的 access_token(Webhook URL 中 access_token= 后面的部分) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_textB | 向钉钉群发送纯文本消息 |
| send_markdownB | 向钉钉群发送 Markdown 格式消息,支持标题、列表、代码块等 |
| send_imageB | 向钉钉群发送图片消息(通过图片 URL) |
| send_newsB | 向钉钉群发送图文消息,包含标题、描述、链接和图片 |
| send_template_cardB | 向钉钉群发送模板卡片消息,支持丰富的卡片布局 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.