2,500+ MCP servers ready to use
Vinkius

DingTalk MCP Server for Claude Code 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add DingTalk as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install DingTalk and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·bash
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add dingtalk --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
DingTalk
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About DingTalk MCP Server

Connect your DingTalk (钉钉) enterprise account to any AI agent and transform your office operations through natural conversation. DingTalk is Alibaba's comprehensive B2B communication and collaboration platform used by millions of organizations for messaging, attendance tracking, approval workflows, and organizational management.

Claude Code registers DingTalk as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where DingTalk data drives decisions without human intervention.

What you can do

  • User Management — Query employee profiles, search users by department, and retrieve contact details instantly
  • Department Exploration — Navigate organizational hierarchy, list departments and sub-departments, understand reporting structures
  • Work Notifications — Send text and markdown formatted messages to employees with rich formatting and clickable links
  • Attendance Tracking — Retrieve check-in/check-out records, verify timesheet data, monitor late arrivals and early departures
  • Approval Workflows — Create new approval instances (leave requests, reimbursements, purchases) and track their progress
  • Approval Status — Query approval process history, identify bottlenecks, and review decision chains
  • Markdown Reports — Send beautifully formatted markdown reports, alerts, and summaries to team members

The DingTalk MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect DingTalk to Claude Code via MCP

Follow these steps to integrate the DingTalk MCP Server with Claude Code.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using DingTalk

Ask Claude: "Using DingTalk, show me...". 10 tools are ready

Why Use Claude Code with the DingTalk MCP Server

Claude Code provides unique advantages when paired with DingTalk through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using DingTalk tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

DingTalk + Claude Code Use Cases

Practical scenarios where Claude Code combined with the DingTalk MCP Server delivers measurable value.

01

CI/CD integration: embed DingTalk tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query DingTalk nightly and generate reports without human intervention

03

Shell scripting: pipe DingTalk outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query DingTalk status endpoints and alert on anomalies

DingTalk MCP Tools for Claude Code (10)

These 10 tools become available when you connect DingTalk to Claude Code via MCP:

01

create_approval_process

g., leave request, reimbursement, purchase order) by creating a new approval instance. Requires the approval template code (process_code) from your DingTalk admin, form component values matching the template structure, and the originator's user ID. Returns the process instance ID for tracking. Use this to automate approval workflows directly from AI conversations. Create a new approval workflow instance in DingTalk

02

get_approval_instance

Returns whether the approval is pending, approved, rejected, or cancelled, along with all reviewer actions and timestamps. Use the process instance ID obtained when creating the approval or from the approval list. Critical for tracking approval progress and understanding bottlenecks. Get status and details of an approval process instance

03

get_attendance_records

Returns timestamps, checkout types (上班签到/下班签退), location data, and whether the attendance was normal or abnormal (late/early leave). Essential for HR teams to monitor attendance patterns, verify timesheet data, or investigate attendance discrepancies. Date format: YYYY-MM-DD. Get employee attendance/checkout records from DingTalk

04

get_department_info

Use this to understand organizational hierarchy, identify department leaders, or map the reporting structure before making decisions about notification routing. Get detailed information about a DingTalk department

05

get_user_info

Use the user ID (userid) which can be obtained from the department user list. Essential for looking up employee details before sending targeted notifications or checking organizational structure. Get DingTalk user profile information by user ID

06

list_all_departments

This is the fastest way to understand the organizational structure, identify department IDs for further queries, and map team hierarchies. Use this before querying users or sub-departments to identify the correct department IDs. List all top-level departments in the DingTalk organization

07

list_sub_departments

Essential for exploring organizational structure, identifying team subdivisions, or mapping the complete departmental hierarchy. Start with department_id 1 to list all top-level departments in your organization. List all sub-departments under a parent department

08

list_users_by_department

Returns user IDs, names, avatars, and basic profile information. Useful for identifying team members before sending group notifications, checking team composition, or understanding departmental structure. Use department ID 1 for the root company directory. List all users in a specific DingTalk department

09

send_markdown_message

Ideal for sending structured reports, formatted alerts, or detailed notifications with clickable links. The title appears as the notification header, while the text body supports full markdown syntax including **bold**, *italic*, [hyperlinks](url), and line breaks. User IDs should be comma-separated. Send a rich formatted markdown message to DingTalk users

10

send_work_notification

Supports text and markdown message types. The message appears in the recipient's DingTalk work notification feed. User IDs should be comma-separated for multiple recipients. This is ideal for sending alerts, reminders, task assignments, or status updates to team members directly through DingTalk. Send a work notification message to DingTalk users

Example Prompts for DingTalk in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with DingTalk immediately.

01

"List all users in department ID 12345."

02

"Send a markdown notification to user1,user2 with title 'Sprint Review' and content about tomorrow's meeting at 2pm."

03

"Check attendance records for user1,user2 from 2024-01-15 to 2024-01-19."

Troubleshooting DingTalk MCP Server with Claude Code

Common issues when connecting DingTalk to Claude Code through the Vinkius, and how to resolve them.

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

DingTalk + Claude Code FAQ

Common questions about integrating DingTalk MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect DingTalk to Claude Code

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.