Tencent Docs MCP

Problem

In automated office workflows, engineers often need to write data, reports, presentation materials, or process documentation into Tencent Docs. However, different document types use different doc_type values, tool prefixes, and parameter constraints. Direct calls can lead to selecting the wrong document type, missing file_id values, blocking the main session with async tasks, deleting child nodes unintentionally, or struggling with errors such as 400006 and -32601. This skill organizes Tencent Docs MCP usage as a routing guide, reducing the cost of choosing among tools for smartcanvas, sheet, slide, smartsheet, and form.

How it works

• Scenario routing: reports and summaries default to smartcanvas; structured data uses smartsheet; calculations and table operations use sheet; Word editing uses docengine; PPT, mind maps, flowcharts, and forms are routed to their corresponding reference documents.
• Core capabilities: it supports document creation, content reading, file management, space node management, image upload, web clipping, unsupported feature reporting, and common interfaces such as get_content.
• Key steps: confirm authorization first, then verify tool schemas with mcporter list tencent-docs. Use parent_id to create documents in a target directory, and poll async tasks such as PPT generation and web clipping in a child session so the main session stays responsive.

Boundaries

• Permission constraints: 400006 usually means token authentication failed, while 400007 indicates insufficient VIP permissions; authorization or permission issues must be resolved first.
• Operational risk: deleting a space node removes only the current node by default; confirm the scope before using recursive deletion.
• Compatibility rules: parameters should follow the MCP tool schema, node_id and file_id can correspond, Markdown content should use UTF-8, and pagination should continue when has_next indicates more results.