How to Use the DingTalk MCP in CrewAI

Q: How do I restrict which DingTalk tools my CrewAI agents can use?

Use the MCPServerHTTP class with a toolfilter. This allows you to expose only sendworknotification while hiding administrative tools like listalldepartments on the MCP Server.

Q: Can multiple CrewAI agents query DingTalk simultaneously?

Yes. CrewAI agents run tasks in parallel, calling getuserinfo or getattendancerecords as needed. The Vinkius sandbox handles concurrent requests efficiently.

Deploy a crew of specialized agents to manage DingTalk departments and automate notifications with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DingTalk MCP to CrewAI

Create your Vinkius account to connect DingTalk to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup DingTalk with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous department mapping via CrewAI

The `list_all_departments` tool allows your research agent to discover your entire corporate structure. The CrewAI agent identifies DingTalk department IDs and passes them to a coordinator agent for deeper analysis over the MCP. Your CrewAI execution agent then runs `list_sub_departments` and `list_users_by_department` to build active rosters. This collaborative crew maps DingTalk reporting lines without manual input.

Multi-agent approval monitoring

The `get_approval_instance` tool enables your auditor agent to track active business requests. This agent polls the status of pending documents and flags any changes to the rest of the crew. If a DingTalk approval is rejected, the CrewAI auditor passes the instance details to a writer agent. The writer agent immediately calls `create_approval_process` to submit an updated request with corrected form values, keeping your operational pipeline moving.

Collaborative incident notifications

The `send_work_notification` tool is used by your alerting agent to alert specific team members. When a system incident occurs, a CrewAI monitoring agent gathers details, and the dispatcher sends the DingTalk alert via the MCP connection. For complex alerts, the dispatcher uses `send_markdown_message` to format log data into tables. The CrewAI crew targets specific DingTalk user IDs fetched via `get_user_info` to avoid spamming the entire channel.

Setup guide

Set up DingTalk MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke DingTalk tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="DingTalk Analyst",
    goal="Access and analyze DingTalk data via MCP.",
    backstory="Expert analyst with direct DingTalk access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent DingTalk transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="DingTalk Analyst",
        goal="Access and analyze DingTalk data via MCP.",
        backstory="Expert analyst with direct DingTalk access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent DingTalk transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect DingTalk now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DingTalk MCP in CrewAI

Use the `MCPServerHTTP` class with a `tool_filter`. This allows you to expose only `send_work_notification` while hiding administrative tools like `list_all_departments` on the MCP Server.

Yes. CrewAI agents run tasks in parallel, calling `get_user_info` or `get_attendance_records` as needed. The Vinkius sandbox handles concurrent requests efficiently.

You don't need to pass raw credentials to your python code. Provide your Vinkius DingTalk MCP Server URL in the agent's `mcps` list, and Vinkius handles the auth.

Yes. You can connect your python environment to the hosted endpoint using standard HTTP transports. This lets your local CrewAI agents trigger `create_approval_process` without local setup.

All transactions pass through our secure V8 Isolate sandbox. Your attendance records and approval forms are processed ephemerally, ensuring zero-trust compliance for your CrewAI execution logs over the MCP.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript