Tencent Docs MCP Plugin

Problem

Office workloads often span docs, sheets, PPT decks, mind maps, and web clippings. When an agent needs to operate Tencent Docs directly, it can be hard to choose the right tool: smartcanvas versus sheet, smartsheet, slide, flowchart, or mind; how to persist Markdown; how to poll asynchronous jobs; and how to diagnose errors. This skill turns those conventions into an executable guide, reducing trial-and-error tool selection and parameter mistakes.

How It Works and Where It Applies

• Scenario routing: reports, notes, and articles default to smartcanvas/MDX; structured data uses smartsheet; calculations, filtering, and statistics use sheet; presentations use slide; diagrams use flowchart and mind.
• Core workflow: inspect tools via mcporter list tencent-docs, then call the matching reference doc. For new docs, prefer create_smartcanvas_by_mdx; for existing docs, use smartcanvas.* tools; for local files, use import_file.sh and manage.async_import.
• Async and shared capabilities: web clipping uses scrape_url followed by scrape_progress; PPT and similar async jobs should be polled in a child session; responses include error and trace_id.
• Boundaries: authorization, VIP, or credit shortfalls surface as 400006, 400007, or 400008; node deletion defaults to the current node, while all deletes recursively; unsupported capabilities should be reported silently rather than guessed.