MCP Dingding Bot MCP Server

MCP Server for send text/markdown message via dingding (aka dingtalk) group custom robot api

Local serverstdioGo

What is the MCP Dingding Bot MCP server?

Most developer tooling work still happens through a UI a human drives. MCP Dingding Bot MCP server moves it into the conversation instead. MCP Server for send text/markdown message via dingding (aka dingtalk) group custom robot api.

The short version

  • Message Notifications — Send various types of DingDing messages (text / markdown)

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Inputs — * text (string): Text content

What it needs from you

Configuration is passed through the environment: DINGTALK_BOT_ACCESS_TOKEN, DINGTALK_BOT_SECRET, YOUR_ACCESS_TOKEN, YOUR_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Dingding Bot's toolset — Inputs — is a fair guide to whether it matches your workflow. It is maintained by Shawyeok; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Dingding Bot's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Inputs* text (string): Text content

How to install the MCP Dingding Bot MCP server

{
  "mcpServers": {
    "gitlab": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DINGTALK_BOT_ACCESS_TOKEN",
        "-e",
        "DINGTALK_BOT_SECRET",
        "shawyeok/mcp-dingding-bot"
      ],
      "env": {
        "DINGTALK_BOT_ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
        "DINGTALK_BOT_SECRET": "<YOUR_SECRET>" // Optional, for robots with signature verification enabled
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DINGTALK_BOT_ACCESS_TOKENCredential the server authenticates with.Yes
DINGTALK_BOT_SECRETCredential the server authenticates with.Yes
YOUR_ACCESS_TOKENCredential the server authenticates with.Yes
YOUR_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Dingding Bot to Inputs.

Frequently asked questions

It connects MCP Dingding Bot to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Inputs) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Dingding Bot directly.