Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
npm install
cp .env.example .env
cp config.example.json config.json2
Register it in Claude Code
claude mcp add -e "DINGTALK_APP_KEY=${DINGTALK_APP_KEY}" -e "DINGTALK_APP_SECRET=${DINGTALK_APP_SECRET}" dingtalk-wiki-mcp -- node /path/to/dingtalk-wiki-mcp/index.jsReplace any placeholder paths in the command with the real path on your machine.
Required:
DINGTALK_APP_KEYDINGTALK_APP_SECRETEnvironment Variables
Set these before running DingTalk Wiki.
VariableDescriptionRequired
DINGTALK_APP_KEYThe App Key for your DingTalk applicationYesDINGTALK_APP_SECRETThe App Secret for your DingTalk applicationYesAvailable Tools (5)
Once configured, DingTalk Wiki gives your AI agent access to:
list_wiki_workspacesList all available Wiki workspaceslist_wiki_nodesList Wiki nodes such as folders and documents within a workspaceworkspace_idcreate_wiki_docCreate a new document, workbook, mind map, or folder in the Wikiworkspace_idnamedoc_typeget_user_infoRetrieve information about a specific useruseridshow_configInspect current local configurationTry It Out
After setup, try these prompts with your AI agent:
→List all my available DingTalk Wiki workspaces.
→Show me the contents of the workspace with ID 'your_workspace_id'.
→Create a new document named 'Weekly Summary' in the workspace 'your_workspace_id'.
→Get the user information for the user with ID 'your_user_id'.
Prerequisites & system requirements
- An MCP-compatible client (Claude Code, Cursor, Windsurf, Claude Desktop, or Codex)
- Node.js 18+ with npm/npx installed
DINGTALK_APP_KEY— The App Key for your DingTalk applicationDINGTALK_APP_SECRET— The App Secret for your DingTalk application
Keep this setup from going cold
Save the docs, env vars, and workflow around DingTalk Wiki in Conare so Claude Code, Codex, and Cursor remember it next time.