- Home
- MCP servers
- DingTalk
DingTalk
- typescript
5
GitHub Stars
typescript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"darrenyao-dingtalk-mcp-server": {
"command": "npx",
"args": [
"-y",
"@darrenyao/server-dingtalk"
],
"env": {
"DINGTALK_APP_KEY": "YOUR_APP_KEY",
"DINGTALK_APP_SECRET": "YOUR_APP_SECRET"
}
}
}
}This MCP server enables Claude to interact with DingTalk workspaces by exposing tools to search users, fetch detailed user information, and send private messages. It lets you automate common DingTalk tasks directly from your MCP client.
How to use
You connect to the DingTalk MCP server from your MCP client and use its tools to perform actions in your DingTalk workspace. The server exposes three core capabilities: search for users, retrieve detailed user information, and send private messages. Use these tools to build workflows that locate the right person, get their profile details, and initiate communication without leaving your MCP client.
How to install
Prerequisites: you need Node.js and Docker installed on your machine. You will also configure a DingTalk application to obtain an AppKey and AppSecret.
Step 1: Prepare your DingTalk app credentials
- Create a DingTalk application in the developer console as an internal enterprise application.
- Note the AppKey and AppSecret for your app.
- Grant the required permissions in your application: userinfo, message, and user list access.
Step 2: Run the MCP server locally using NPX
- Use your AppKey and AppSecret to start the server via NPX as shown below.
{
"mcpServers": {
"dingtalk": {
"command": "npx",
"args": [
"-y",
"@darrenyao/server-dingtalk"
],
"env": {
"DINGTALK_APP_KEY": "your_app_key",
"DINGTALK_APP_SECRET": "your_app_secret"
}
}
}
}
Step 3: Run the MCP server using Docker
- If you prefer Docker, run the container with the provided environment variables.
{
"mcpServers": {
"dingtalk": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DINGTALK_APP_KEY",
"-e",
"DINGTALK_APP_SECRET",
"mcp/dingtalk"
],
"env": {
"DINGTALK_APP_KEY": "your_app_key",
"DINGTALK_APP_SECRET": "your_app_secret"
}
}
}
}
Additional sections
Configuration and security notes: ensure your DingTalk app is installed in the enterprise and that the app has the necessary permissions. Keep your AppKey and AppSecret secure and avoid exposing them in public environments.
Troubleshooting: if you encounter permission errors, verify that the app has the required permissions, is installed in the enterprise, and that credentials are correct.
Notes: environment variables are required for both deployment methods. The server exposes a set of tools you can call from your MCP client to perform common DingTalk operations.
Available tools
dingtalk_search_users
Search for DingTalk users using a query string. Optional exact_match flag to enforce precise results.
dingtalk_get_user_info
Fetch detailed information about a user by user_id, including name, employee number, department, join date, and contact details.
dingtalk_send_message
Send a private message to a DingTalk user by providing the recipient name and message content.