DingTalk Docs MCP Assistant

Problem

Operating DingTalk documents inside an Agent is not just one API call. The hard part is mapping intent to the right node type and write path: text is adoc, spreadsheets are axls, shortcuts are dlink, files may need original-format upload, and a default workspace URL may be missing without node IDs.

How It Works

The skill depends on a DingTalk Docs MCP server named dingtalk-doc. Setup can register the MCP service and store a default workspace URL in references/dingtalk.config, then read that file or environment variables before acting. Common operations include:

• search_documents, list_nodes, and get_document_info for locating targets
• get_document_content for reading adoc text
• create_document and update_document for online text documents
• list_document_blocks plus block insert/update/delete for precise edits
• get_file_upload_info, HTTP PUT, and commit_uploaded_file for HTML, images, PDF, Office, and other files
• submit_export_job and query_export_job for asynchronous export

Boundaries

create_document and update_document only support adoc documents and have a 10,000-character Markdown limit. Content over 9,500 characters should be split or uploaded as a raw .md file, not converted silently. Tables, slides, mind maps, whiteboards, and shortcuts are not readable as adoc content. mermaid blocks do not automatically become native DingTalk drawings. Write operations should confirm target, filename, and method; deletes usually go to the recycle bin.