DingTalk
China · Collaboration · Status Active · Cross-border (measured) N/A
Data updated: 2026-10-29 14:00| Company | DingTalkOfficial docs · 2026-10-29 · source |
|---|---|
| Product | DingTalkOfficial docs · 2026-10-29 · source |
| Region | ChinaOfficial docs · 2026-10-29 · source |
| Category | CollaborationOfficial docs · 2026-10-29 · source |
| Type | MCP serverOfficial docs · 2026-10-29 · source |
| Transport | stdioOfficial docs · 2026-10-29 · source |
| Package | npm: dingtalk-mcpOfficial docs · 2026-10-29 · source |
| Latest version | 1.1.21Official docs · 2026-10-29 · source |
| Auth | Verified businessOfficial docs · 2026-10-29 · source |
| Account requirements | DingTalk Developer + Enterprise Internal Application Client ID/SecretOfficial docs · 2026-10-29 · source |
| Cross-border (measured) | N/ATANDIU measured · 2026-10-29 · source |
| Status | ActiveTANDIU measured · 2026-10-29 · source |
| Listed on | Not listedOfficial docs · 2026-10-29 |
| Redistribution | UnclearOfficial docs · 2026-10-29 · source |
| Notes | Contacts, departments, robot messages/DING, to-dos, schedules, check-ins, work notifications, project management, logs, etc., enabled by grouping under ACTIVE_PROFILES, with each group requiring corresponding permission points on the open platform. MaaS also has hosted items like calendar/email/approval published by the official DingTalk account.Official docs · 2026-10-29 · source |
| Official docs | Docs · Home |
Every field shows its evidence (official docs / TANDIU measured), check date and source. The handshake is an MCP initialize only, with no credentials and no tool calls.
HISTORY
Change history
- BaselineFirst record of 16 fields