DingDing

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

typescript

GitHub Stars

typescript

Language

6 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": {
    "shawyeok-mcp-dingding-bot": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DINGTALK_BOT_ACCESS_TOKEN",
        "-e",
        "DINGTALK_BOT_SECRET",
        "shawyeok/mcp-dingding-bot"
      ],
      "env": {
        "DINGTALK_BOT_SECRET": "<YOUR_SECRET>",
        "DINGTALK_BOT_ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>"
      }
    }
  }
}

You are running an MCP server that integrates with the DingDing / Dingtalk Bot API to send message notifications in groups. This server lets you post plain text or markdown messages to a DingDing group and supports optional mentions of all members. It is designed to be run locally (via Docker or NPX) and connected to your DingDing bot credentials.

How to use

Start by choosing how you want to run the server. You can run it via Docker or with NPX. In either case, you must provide your DingDing group bot credentials so the server can post messages to your group.

How to install

Prerequisites: ensure you have Docker installed if you plan to run the Docker command. If you prefer NPX, you only need Node.js and npm to run NPX commands.

Configuration and usage examples

Configure your DingDing bot credentials in the environment variables you pass to the MCP server. The required value is the access token. You may also set a signature secret if your bot requires verification.

Examples of run configurations

{
  "mcpServers": {
    "dingding_docker": {
      "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
      }
    },
    "dingding_npx": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-dingding-bot"
      ],
      "env": {
        "DINGTALK_BOT_ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
        "DINGTALK_BOT_SECRET": "<YOUR_SECRET>" // Optional, for robots with signature verification enabled
      }
    }
  }
}

Environment variables

The following environment variables are used by the MCP server. Provide their values when you run the server.

Tools and actions

send_text_message: Send a plain text message to a DingDing group. Inputs: text, optional atAll to notify everyone.
send_markdown_message: Send a markdown formatted message to a DingDing group. Inputs: title, text, optional atAll to notify everyone.

Build and run notes

If you choose Docker, build is not required; you pull and run the image with the provided configuration. If you choose NPX, you rely on the package to fetch and run the MCP server on demand.

Security considerations

Keep your DingDing bot access token and secret secure. Do not expose them in public logs or shared configurations.

Troubleshooting

If messages fail to send, verify that the access token (and secret if used) are correct and that the bot has permission to post in the target group. Check that the MCP server is running and reachable by your client.

Available tools

send_text_message

Send a plain text message to a dingding group. Optionally @ all members using atAll.

send_markdown_message

Send a markdown formatted message to a dingding group. Include a title and markdown content. Optionally @ all members using atAll.

Built by

VeilStrat

AI signals for GTM teams