2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add DingTalk as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="dingtalk_agent",
            tools=tools,
            system_message=(
                "You help users with DingTalk. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use DingTalk tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the DingTalk MCP Server with AutoGen.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 10 tools from DingTalk automatically

Why Use AutoGen with the DingTalk MCP Server

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

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use DingTalk tools to solve complex tasks

02

Role-based architecture lets you assign DingTalk tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive DingTalk tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes DingTalk tool responses in an isolated environment

DingTalk + AutoGen Use Cases

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

01

Collaborative analysis: one agent queries DingTalk while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from DingTalk, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using DingTalk data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process DingTalk responses in a sandboxed execution environment

DingTalk MCP Tools for AutoGen (10)

These 10 tools become available when you connect DingTalk to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

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

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

DingTalk + AutoGen FAQ

Common questions about integrating DingTalk MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call DingTalk tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect DingTalk to AutoGen

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