MCP capabilities and task reference
Use this reference to choose the right operation when working through an external assistant. The connected server supplies its current tool schemas; use those schemas for exact arguments rather than relying on a fixed tool count.
Find and read documentation
| Task | Tools |
|---|---|
| Identify your account and available Spaces | get-user-info, list-spaces |
| Browse pages in a Space | list-space-documents |
| Search one Space or all accessible Spaces | search-space-documents, global-search |
| Read a complete page | get-space-document |
Start with search, then read the relevant document before proposing changes. A search excerpt is not the whole page. Space identifiers are numeric IDs, not public URL slugs.
Create and organize content
Use create-space-document or update-space-document for Markdown page content, with type: "markdown" where required by the tool. Space-item tools manage folders, links, movement, copying, sharing, and deletion. Space tools manage the container itself. Deleting a Space is different from deleting one item inside it.
export-space-items-markdown returns selected content to the assistant. Use DocuWriter’s browser export controls for downloadable PDF or ZIP files. Creating a share link exposes content through a public URL; review the intended audience first.
Generate documentation
list-generators describes available operations. Supplied-code tools cover documentation, tests, comments, optimization, diagrams, OpenAPI, and language conversion. Repository README and selected-file documentation require an imported repository. Codebase generation creates a Space with queued documentation work.
Full Tree generation has a review step: retrieve an existing preview with get-full-tree-documentation-preview, inspect it, and submit generate-full-tree-documentation only after accepting that tree. Pass the returned acceptance hash. Creating the first preview and editing its structure remain browser tasks. A queued workflow is not a completed document.
Existing generation tools list, read, rename, archive, restore, select a definitive version, add results to a Space, and create share links. Use archive/restore for generation history rather than assuming a delete operation exists.
Maintain the workspace
Other tool families cover Autopilot links and suggestions, team members and invitations, webhook subscriptions and delivery logs, AI preferences, and provider-connection status. Read the target resource before a change and verify the result afterward. Autopilot access still follows your plan and team permissions.
Complete browser-only steps
Provider consent, repository import and initial selection, local uploads, billing, password/security settings, API-token secrets, and browser downloads use DocuWriter’s UI. An assistant can guide you there without claiming it completed the action. External clients control MCP tool confirmations; see approval behavior.
Updated