Skip to main content
Glama
sfyyy

Claude Code DingTalk MCP Server

by sfyyy

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
dingtalk_configureC

Configure DingTalk webhook settings

dingtalk_send_textC

Send a text message to DingTalk group

dingtalk_send_markdownC

Send a markdown message to DingTalk group

dingtalk_send_linkC

Send a link message to DingTalk group

dingtalk_notify_session_endB

Send a session completion notification with automatic stats

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: configure webhook settings, notify session end with stats, and send three different message types (link, markdown, text). There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent 'dingtalk_verb_noun' pattern with snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of DingTalk integration. Each tool serves a specific function (configuration, notifications, messaging), and none feel redundant or missing for the apparent scope.

Completeness4/5

The toolset covers core messaging and notification workflows for DingTalk, including configuration and different message formats. A minor gap might be the lack of tools for reading or managing incoming messages, but the surface is largely complete for sending notifications and messages.

Maintenance

ActivityInactive
ResponsivenessNo issues