dingtalk

This MCP server implements a DingTalk integration that lets Claude interact with a DingTalk workspace. It exposes three tools: dingtalk_search_users, which searches for DingTalk users using a query keyword (with an optional exact_match flag); dingtalk_get_user_info, which retrieves detailed information for a given user_id; and dingtalk_send_message, which sends a direct message to a specified user by name with provided content. To use these tools, launch the MCP server via your preferred method (for example using npx with the provided configuration) and call the tools from Claude as you would with other MCP tools. Ensure your DingTalk application credentials (AppKey and AppSecret) are properly configured in the environment variables so the server can authenticate with the DingTalk APIs.

Prerequisites:

• Node.js installed on your machine (version compatible with the MCP server package).
• Access to an DingTalk developer account to create an app and obtain AppKey and AppSecret.

Install and run:

1. Ensure you have npm and npx available in your shell.

2. Start the MCP server using the provided npx configuration. Example:

   npx -y @darrenyao/server-dingtalk

3. When prompted or in your environment, set the required environment variables for DingTalk:

   • DINGTALK_APP_KEY: your_app_key
   • DINGTALK_APP_SECRET: your_app_secret

4. Verify the server starts successfully and is reachable by Claude/your MCP runner. You should see logs indicating the three tools are available (dingtalk_search_users, dingtalk_get_user_info, dingtalk_send_message).

Notes:

• If you prefer Docker, you can adapt the provided configuration to run the corresponding container with the needed environment variables.

Tips and caveats:

• Ensure your DingTalk app has the required permissions (userinfo, message, user) enabled in the DingTalk developer console.
• Double-check that AppKey and AppSecret are correctly configured and that the app is installed within your enterprise.
• When debugging permissions errors, verify that the app has been granted access to the necessary scopes and that the credentials are not expired.
• The tools expect specific parameter names; for example, dingtalk_search_users requires query and may accept exact_match as an optional boolean. dingtalk_get_user_info requires user_id. dingtalk_send_message requires user and content.
• Keep your credentials secure and avoid committing them to version control. Consider using a secrets manager or environment variable injection in your deployment environment.