Mcp Server Dingtalk

Created By
1liba year ago
A Model Context Protocol (MCP) server for DingTalk integration.
Overview

What is Mcp Server Dingtalk?

Mcp Server Dingtalk is a Model Context Protocol (MCP) server designed for integrating with DingTalk, enabling automated messaging and bot functionalities.

How to use Mcp Server Dingtalk?

To use the server, set up your bot configurations in the environment variables and run the server using Node.js with the command: npx mcp-server-dingtalk.

Key features of Mcp Server Dingtalk?

  • 🤖 DingTalk bot message sending capabilities
  • 📦 Supports multiple message types including text, link, markdown, actionCard, and feedCard
  • 🔐 Secure webhook signing with HMAC-SHA256
  • ⚡ Built with Vite for fast development and optimized production builds
  • 🎯 TypeScript support with strict type checking

Use cases of Mcp Server Dingtalk?

  1. Automating notifications in DingTalk chat groups.
  2. Sending rich media messages to enhance communication.
  3. Integrating with other services to provide real-time updates in DingTalk.

FAQ from Mcp Server Dingtalk?

  • What are the prerequisites for using Mcp Server Dingtalk?

You need Node.js 18+ and pnpm (recommended) or npm.

  • Can I customize the message types?

Yes! You can send various types of messages including text, links, and markdown.

  • Is there a license for Mcp Server Dingtalk?

Yes, it is licensed under MIT.

Server Config

{
  "mcpServers": {
    "mcp-server-dingtalk": {
      "transport": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-dingtalk"
      ],
      "env": {
        "DINGTALK_BOT_CONFIGS": "[{\"name\": \"your-bot-name\", \"accessToken\": \"your-access-token\", \"signSecret\": \"your-sign-secret\"}]"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
1lib
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago