npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sputnicyoji/dingtalk-workspace-mcp

v0.0.5

Published

dws-driven, dynamic, full-coverage DingTalk MCP server. Host-agnostic. Auto-syncs with dws upgrades, zero maintenance.

Readme

@sputnicyoji/dingtalk-workspace-mcp

dws-driven, dynamic, full-coverage DingTalk MCP server. Host-agnostic. Auto-syncs with dws upgrades — zero maintenance.

What it does

Spawns the dws CLI under the hood, walks its --help tree (or dws schema --format json when authenticated), and exposes every dws leaf command as a fully-typed MCP tool named dingtalk.<service>.<...>.<action>.

When dws ships new products / commands, restart this MCP server and they appear. No code changes here.

Install

You don't install this package directly — it's invoked via npx -y from your MCP host config.

Prerequisites (all hosts):

# 1. Install dws (one-time)
# macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/DingTalk-Real-AI/dingtalk-workspace-cli/main/scripts/install.sh | sh
# Windows (PowerShell):
irm https://raw.githubusercontent.com/DingTalk-Real-AI/dingtalk-workspace-cli/main/scripts/install.ps1 | iex

# 2. Authenticate
dws auth login

Wire into your MCP host

mcp.json (or your host's equivalent — Claude Desktop, Cursor, Codex, ...):

{
  "mcpServers": {
    "dingtalk": {
      "command": "npx",
      "args": ["-y", "@sputnicyoji/dingtalk-workspace-mcp"]
    }
  }
}

YAML-config hosts use the same shape under their own key:

mcp_servers:
  dingtalk:
    command: "npx"
    args: ["-y", "@sputnicyoji/dingtalk-workspace-mcp"]
    timeout: 180

That's it. Restart the host. ~80 dingtalk.* tools become available.

CLI flags

-v, --verbose         enable verbose logging to stderr
    --timeout <sec>   per-tool-call timeout (default 120, env DINGTALK_MCP_TIMEOUT)
    --version         print version
-h, --help            show help

Behavior summary

| Situation | What happens | |-----------|--------------| | dws not in PATH | server exits 1 with install link | | dws version < 1.0.7 | server exits 1, prompts dws upgrade | | dws not authenticated | server starts, exposes 80+ tools (parsed from --help) + a dingtalk.bootstrap diagnostic tool | | dws authenticated | server starts, prefers richer dws schema JSON when available | | dws schema upgrade breaks parser | help-tree fallback keeps the server alive | | Single tool call exceeds timeout | returns {isError: true, code: TIMEOUT} — no auto-retry | | dws auth expires mid-session | returns {isError: true, code: AUTH_EXPIRED} with retry guidance |

Architecture

MCP host  ──stdio──>  this MCP server  ──spawn──>  dws  ──HTTPS──>  DingTalk Open Platform

Server is stateless. All token / auth / business logic lives in dws itself.

Develop

npm install
npm run typecheck
npm test               # 80 vitest tests, ~90% coverage
npm run test:coverage  # full coverage report
npm run build          # tsc → dist/
node smoke-test.mjs    # end-to-end: spawn server, send tools/list (real dws required)

License

MIT © Yoji