dingtalk_get_user_info
Get detailed information about a specific DingTalk user
LABSCO SUMMARY
Three tools that make a notification addressable by a person's name rather than by an ID you had to know already.
The order is fixed by what each call accepts: dingtalk_search_users takes a keyword and hands back user IDs, dingtalk_get_user_info takes one of those IDs, and dingtalk_send_message needs the user before it can deliver content. dingtalk_search_users returns a paged result with hasMore and totalCount rather than a single answer, so an ambiguous name still has to be narrowed before anything is sent. The surface stops at private messages to one user — there is no group or channel call here.
What it is
A small DingTalk messaging server, 3 tools covering user lookup and direct messages for one registered DingTalk app.
What you get
- Name-to-ID resolution: dingtalk_search_users searches the directory by keyword, exactly or loosely, and returns the matching user IDs together with a total count and a has-more flag.
- Profile detail for a resolved user: dingtalk_get_user_info takes a user_id and returns that user's details.
- Direct delivery: dingtalk_send_message posts private message content to a specific user.
Requirements
A DingTalk app registered on the account whose directory you are searching, with DINGTALK_APP_KEY and DINGTALK_APP_SECRET in the environment.
Setup effort
One command plus credentials — npx -y @darrenyao/server-dingtalk, then supply credentials
USE CASES
01
Reaching a colleague when all you have is their name
Resolve the name to user IDs, confirm you have the right person from their profile, and send the message to that user directly.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
dingtalk_search_users
Searches DingTalk users and returns the matching user IDs, with a total count and a flag for whether more results remain.
dingtalk_send_message
Send a private message to a specific DingTalk user
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- DINGTALK_APP_KEY in your environment
- DINGTALK_APP_SECRET in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @darrenyao/server-dingtalkMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"dingtalk": {
"command": "npx",
"args": [
"-y",
"@darrenyao/server-dingtalk"
],
"env": {
"DINGTALK_APP_KEY": "<YOUR_DINGTALK_APP_KEY>",
"DINGTALK_APP_SECRET": "<YOUR_DINGTALK_APP_SECRET>"
}
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · TERMINAL
git clone https://github.com/darrenyao/dingtalk-mcp-server.git
cd dingtalk-mcp-server
docker build -t mcp/dingtalk -f Dockerfile .CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"dingtalk": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DINGTALK_APP_KEY",
"-e",
"DINGTALK_APP_SECRET",
"mcp/dingtalk"
],
"env": {
"DINGTALK_APP_KEY": "<YOUR_DINGTALK_APP_KEY>",
"DINGTALK_APP_SECRET": "<YOUR_DINGTALK_APP_SECRET>"
}
}
}
}
