DingTalk MCP. Manage entire office workflows and attendance tracking.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
DingTalk MCP connects your agent to Alibaba's enterprise communication platform for managing internal operations. Use it to check employee attendance, map complex department hierarchies, send formatted announcements, and run automated approval workflows—all from a single chat window.
What your AI agents can do
Create approval process
Start a new workflow instance for things like leave requests or purchases by feeding it the required template code and user IDs.
Get approval instance
Checks if an existing approval process is pending, approved, rejected, or cancelled, giving you all the reviewer actions taken.
Get attendance records
Retrieves timestamps and checkout types for employees to verify attendance patterns across a date range.
List all departments, sub-departments, and retrieve detailed information about any specific organizational unit.
Search for individual employee details using their user ID or query a list of users within a specified department.
Pull check-in/check-out records to monitor who is working, when they arrived, and if any shifts were marked as late or early.
Start new official processes—like reimbursement requests or vacation time off—and track them until completion.
Broadcast announcements, formatted alerts, or detailed reports to multiple team members with rich text and links.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
DingTalk: 10 Tools for Enterprise Operations
These ten tools let you map departmental structures, check employee attendance, initiate formal approval processes, and send structured communications through the DingTalk platform.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using DingTalk on Vinkius019d842ecreate approval process
Start a new workflow instance for things like leave requests or purchases by feeding it the required template code and user IDs.
019d842eget approval instance
Checks if an existing approval process is pending, approved, rejected, or cancelled, giving you all the reviewer actions taken.
019d842eget attendance records
Retrieves timestamps and checkout types for employees to verify attendance patterns across a date range.
019d842eget department info
Provides detailed information about any department, helping you understand its role in the company structure.
019d842eget user info
Looks up a specific employee's profile details using only their user ID before sending them targeted notifications.
019d842elist all departments
Gives you the complete list of top-level departments in the organization, which is needed to start any structural query.
019d842elist sub departments
Drills down into a parent department to map out every single team division and sub-group beneath it.
019d842elist users by department
Gathers the list of all users, names, and basic profiles belonging to a specific departmental group.
019d842esend markdown message
Sends highly structured reports or detailed alerts using full markdown formatting (like bold text and links) to multiple recipients.
019d842esend work notification
Posts a standard message, reminder, or task assignment directly into the recipient's work notification feed for immediate visibility.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with DingTalk, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DingTalk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Today, managing office logistics means logging into three separate platforms.
Think about it. To check a team member's time off status, you might have to open the HRIS portal, pull up their employee profile, then cross-reference that with the department directory just to confirm they are still part of the group. If you need to send an update based on that data, you then switch over to your messaging app and paste a formatted message. It's clicking through four or five different screens for one simple outcome.
With this MCP, all those steps happen in the chat window. You simply ask: 'What's John Doe's status?' The agent pulls that data from the source systems, figures out which department he belongs to, and gives you a plain-language answer without you ever leaving your conversation interface.
The `create_approval_process` tool makes formal sign-offs conversational.
Before this MCP, getting approval meant filling out paper forms, emailing them to a manager who would then forward it to finance, creating physical bottlenecks and requiring constant manual follow-up. You had no single source of truth for the process's exact status or which step was stalled.
Now, you tell your agent what needs approving—a purchase order, a leave request, anything governed by an internal template. The system creates the official digital instance in DingTalk and tracks it automatically. It’s instant workflow governance.
What you can do with this MCP connector
Managing an office today means jumping between three different systems: the HR database, the team chat app, and the workflow portal. This MCP makes that jump obsolete. It lets your AI agent act as a centralized operations assistant for everything internal. Need to know who reports to whom? Ask it.
Want to send a formatted announcement about a policy change? Do it without copy-pasting markdown into a separate app. You can track an employee's entire lifecycle—from checking their initial attendance records to initiating a leave request, and then broadcasting the final approval status to the whole team. The real power comes when you chain this MCP with other services in the Vinkius catalog; for example, triggering a payment record update immediately after tracking a successful purchase order approval.
You don't need multiple logins or complex integrations. Just connect once from your preferred AI client and start running core business processes through natural conversation.
019d842e-46c2-7153-afa9-1d5cfa8cea18 
How DingTalk MCP Works
- 1 Subscribe to the DingTalk MCP on Vinkius.
- 2 Provide your required DingTalk App Key and Secret credentials.
- 3 Start by asking your agent to perform an action, like listing all departments or checking attendance for a specific date range.
The bottom line is you get one chat interface that handles HR lookups, communication broadcasts, and complex process tracking without requiring any direct access to the DingTalk app itself.
Who Is DingTalk MCP For?
Operations leaders who spend too much time manually cross-referencing timesheets against org charts. Managers who get frustrated having to log into three different systems just to approve a single expense claim.
You use this MCP to pull attendance records and verify time sheets, quickly identifying any discrepancies or tracking late arrivals across an entire department.
You manage team flow by initiating purchase requests or leave applications through the system. You then check the status of these workflows without needing to open a dedicated portal.
You map out reporting lines using department structure tools, and then send formatted markdown messages containing company-wide alerts or summaries.
What Changes When You Connect
- Stop guessing who reports to whom. Use the departmental listing tools to map out the full organizational structure before making any decisions about communication routing.
- Track compliance with
get_attendance_records. You can verify time sheets and instantly spot patterns of late arrivals or missing check-ins without running manual payroll checks. - Automate approvals from start to finish. Use
create_approval_processto kick off a purchase request, then useget_approval_instanceto track its progress in the chat window until it's finalized. - Broadcast formatted updates with
send_markdown_message. Instead of sending plain text emails, you can deliver rich reports that include bold headers and clickable links directly into DingTalk. - Improve team awareness by using
list_users_by_departmentto get a current roster. This ensures any group notification or task assignment goes out to the right people every time.
Real-World Use Cases
New Hire Onboarding
An Ops Lead needs to confirm who is on the team. They ask the agent to list all users in the Engineering department, then use get_user_info for each person's profile before sending a group welcome notification via send_work_notification.
Expense Report Bottleneck
A manager needs to know why an expense report is stuck. They use the agent to check the approval status using get_approval_instance, immediately identifying which reviewer hasn't acted, and then they can send a reminder via send_markdown_message.
Compliance Audit Prep
HR needs an attendance snapshot for last quarter. They run the report using get_attendance_records, which pulls all check-in/check-out data, letting them quickly verify compliance without pulling CSVs from a backend system.
Department Restructure
A leader needs to know if they should merge two teams. They first run list_all_departments and then use list_sub_departments on both departments to map out their full current hierarchies before making a decision.
The Tradeoffs
Sending general announcements
Trying to send a critical alert about a mandatory system update to everyone, but only knowing the department ID and not the user IDs.
→
First, run list_users_by_department using the correct department ID. Once you have that list of valid user IDs, use those specific IDs when calling send_markdown_message.
Starting a complex approval
Manually filling out a paper form for a reimbursement and having to chase down signatures over email.
→
Use the agent to execute create_approval_process. It handles the entire digital instance creation, ensuring you capture the required process code and user IDs in one chat command.
Checking current roster size
Asking for a list of 'all employees' which might include contractors or archived users who aren't relevant to active workflows.
→
Always start by running list_all_departments, then drill down using list_sub_departments to narrow the scope, and finally use list_users_by_department for an accurate count.
When It Fits, When It Doesn't
Use this MCP if your core process involves tracking structured internal movements: approvals, attendance, or departmental reporting lines. It’s built for auditable processes where knowing who was involved and when it happened matters more than just sending a message. Don't use it if you simply need to send an ad-hoc reminder; in that case, using send_work_notification is fine. But if the communication is related to an HR function—like confirming who can approve a budget or checking timesheet data—you must use its specific workflow tools like get_attendance_records and create_approval_process. It's designed for governance, not just chatting.
Common Questions About DingTalk MCP
How do I use `list_users_by_department` with this MCP? +
You must provide the department ID number first. This tool then returns a list of user IDs, names, and basic profiles for everyone belonging to that specific department.
Can I use `get_attendance_records` to find who was late? +
Yes. It pulls the full check-in/check-out history for a date range and specifically flags any records marked as abnormal, like being late or leaving early.
What's the difference between `send_markdown_message` and `send_work_notification`? +
Send_markdown_message is for rich reports and detailed alerts where you need full formatting. Send_work_notification is better for simple, immediate reminders or status updates that pop into a user's feed.
Does the MCP help me map department hierarchies? +
Yes. You can use list_all_departments to see top-level units and then use list_sub_departments to drill down and understand every nested team structure.
When I use `get_user_info`, what security measures protect my DingTalk credentials? +
The platform uses a zero-trust proxy. Your keys only pass through in transit and are never stored on disk, so your credentials stay secure no matter how many times you run the tool.
If I initiate an approval with `create_approval_process`, how do I track its status or find bottlenecks? +
You call get_approval_instance using the process ID. This function provides a full audit trail, showing if the request is pending, approved, rejected, and who took action when.
When running `list_sub_departments`, what should I use as the starting parent department ID? +
You generally start with the top-level department ID, usually '1'. This ensures you map out all foundational divisions before you dive into specific sub-teams or reporting structures.
If `list_users_by_department` returns a huge list of users, how does it handle pagination? +
The MCP manages large datasets by providing paginated results. The output includes the necessary tokens or cursors you'll need to fetch all remaining user data in subsequent calls without hitting limits.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.