DocuWriter.ai

Use this when the user wants to share a Space page/document, folder, or external link with a public URL. State-changing public-link action: creates and returns a signed public share link after authorization. Requires owned Space access, space_id, item_id, and optional expiration.

create-space-item-share-link

Use this when the user wants to create a Space page/document, folder, or external link inside an existing Space. State-changing: creates the item directly after authorization. Requires numeric space_id, item type, title, and content or URL when relevant.

create-space-item

Use this when the user wants to link an authorized provider repository to a Space for Autopilot sync. After authorization, this state-changing external action creates the link with triggers, path filters, notifications, or auto-apply settings and requires Enterprise access.

create-space-repository-link

Use this when the user wants to create a new documentation Space or knowledge base container. State-changing: creates the Space directly after the MCP client authorizes the call. Requires a Space name and may include description, public visibility, and slug.

create-space

Use this when the user wants to add a webhook, callback URL, n8n/Zapier endpoint, or integration subscription for supported DocuWriter events. State-changing external action: creates the subscription after authorization. Use list-webhook-events first for valid event keys; webhook test dispatch is not exposed.

create-webhook-subscription

Use this when the user explicitly wants to delete one existing Space document/page. Destructive state-changing action: deletes the document directly after authorization. Requires the document ID from list-space-documents or search results; use delete-space-items for folders or bulk item deletion.

delete-space-document

Use this when the user wants to delete one or more Space pages, documents, folders, or external links from a Space. Destructive state-changing action: deletes the selected items directly after the MCP client authorizes the call. Requires numeric space_id and item_ids from list-space-documents.

delete-space-items

Use this when the user wants to remove an Autopilot repository link from a Space. Destructive external-provider action: deletes the link after authorization and may remove provider webhook configuration. Requires Enterprise access, manageable Space permission, space_id, and link_id.

delete-space-repository-link

Use this when the user explicitly wants to delete a whole documentation Space. Destructive state-changing action: removes the manageable Space directly after the MCP client authorizes the call. Requires numeric space_id from list-spaces and should not be used for deleting individual pages.

delete-space

Use this when the user wants to remove a webhook subscription or stop sending events to an endpoint. Destructive external action: deletes the owned subscription after authorization. Requires subscription_id from list-webhook-subscriptions; webhook test dispatch is not exposed.

delete-webhook-subscription

Use this when the user wants to pause, turn off, or disable an Autopilot repository link for a Space. State-changing external-provider action: disables the link and attempts to remove the provider webhook after authorization. Requires Enterprise access, manageable Space permission, space_id, and link_id.

disable-space-repository-link

Use this when the user wants to reject, dismiss, remove from review, or discard one Autopilot/repository-sync documentation suggestion. Destructive state-changing action: marks the pending suggestion discarded directly after authorization. Requires suggestion_id from list-space-suggestions.

discard-space-suggestion

Use this when the user wants to turn on or resume an existing Autopilot repository sync link for a Space. State-changing external-provider action: enables the link and registers the provider webhook after authorization. Requires Enterprise access, manageable Space permission, provider access, space_id, and link_id.

enable-space-repository-link

Use this when the user wants a Markdown export of selected Space pages, folders, or docs that can be returned in the MCP response. Read-only: returns merged Markdown without changing Space content. Use browser guidance for PDF, ZIP, or download-only export flows.

export-space-items-markdown

Use this when the user supplies source code and asks to add inline comments, docblocks, docstrings, or code annotations. State-changing generation action: consumes AI credits, creates a generation, and returns commented code after authorization. Use browser guidance for file uploads.

generate-code-comments

Use this when the user supplies source code and asks to generate markdown documentation, explain code, or document one or more files. State-changing generation action: consumes AI credits, creates a generation, and returns documentation after authorization. Use browser guidance for local upload or repository/full-tree flows.

generate-code-documentation

Use this when the user supplies source code and asks to generate unit, feature, integration, or framework-specific tests. State-changing generation action: consumes AI credits, creates a generation, and returns test code after authorization. Use browser guidance for local uploads or repository-wide test generation.

generate-code-tests

Use this when the user wants a new documentation Space built from selected files in an imported repository. After authorization, this state-changing action consumes AI credits, creates a private Space, links the repository, and queues per-file jobs using repository_id and selected_files.

generate-codebase-documentation

Use this when the user supplies source files and wants the generated documentation saved directly in an existing Space. After authorization, this state-changing action consumes AI credits, creates a generation, and writes a document to the specified space_id.

generate-and-add-documentation

Use this when the user has reviewed a full-tree preview and asks to create its documentation Space. After authorization, this state-changing action consumes AI credits, creates a private linked Space, and queues documentation from the stored preview using repository_id and accepted_tree_hash.

generate-full-tree-documentation

Use this when the user supplies API source code and asks for an OpenAPI or Swagger specification. After authorization, this state-changing action consumes AI credits, creates a generation, and returns OpenAPI JSON; it accepts one source_code file or multiple files entries.

generate-swagger-api

Use this when the user wants one markdown document generated from selected files in an imported repository. After authorization, this state-changing action consumes AI credits and creates a generation using numeric repository_id and selected_files, with optional Space saving.

generate-repository-documentation

Use this when the user asks to generate or refresh a README for an imported repository. After authorization, this state-changing action consumes AI credits, creates a generation, and can save it to a Space; it requires the numeric repository_id.

generate-repository-readme

Use this when the user wants release notes from two branches of a connected provider repository. After authorization, this state-changing action compares base_branch with compare_branch, consumes AI credits, creates a generation, and can save it to a Space.

generate-repository-release-notes

Use this when the user supplies source code and asks for UML, Mermaid, sequence, class, component, or architecture diagrams. State-changing generation action: consumes AI credits, creates a generation, and optionally writes markdown to a Space after authorization. Use browser guidance for local uploads or full repository diagrams.

generate-uml-diagram

Use this when the user asks which DocuWriter.ai account is connected or whether it can run a generator. Read-only: returns the account name and a can_generate boolean without changing account data.

get-user-info

Use this when the user wants to view current AI writing guidelines, templates, strict mode, generator scope, or team-enforced generation preferences. Read-only: returns effective personal/team preferences and whether they are editable without changing settings.

get-ai-preferences

Use this when the user wants to inspect an existing full-tree documentation preview before creating a Space. Read-only: returns repository details, tree titles, page counts, source-file counts, credit impact, and an acceptance hash for the numeric repository_id.

get-full-tree-documentation-preview

Use this when the user wants to read a specific generated output/result, inspect version metadata, see generated markdown, or choose a version for later actions. Read-only: returns the generation by numeric generation_id without changing it.

get-generation

Use this when the user asks what changed in a Space, who changed settings, sync events, document actions, or recent activity. Read-only Enterprise feature: returns the Space activity/audit log newest first. Requires numeric space_id and Enterprise access.

get-space-activity-log

Use this when the user wants to read the full markdown content of a specific Space document/page after search or listing. Read-only: returns the selected document without changing content. Requires the document ID from list-space-documents, search-space-documents, or global-search.

get-space-document

Use this when the user wants to invite a teammate by email with an editor or viewer role. After authorization, this state-changing external action creates a pending invitation and sends one email; invitation acceptance occurs in the browser.

invite-team-member

Use this when the user asks to find generated outputs, generation history, previous results, archived items, or IDs for later generation actions. Read-only: lists visible personal/team generations and can include previews or full content without changing anything.

list-generations

Use this when the user asks which DocuWriter.ai generators are available or what inputs a generator requires. Read-only: returns generator identifiers, required inputs, credit behavior, Space output behavior, and browser-only setup boundaries without running a generator.

list-generators

Use this when the user asks whether GitHub, GitLab, Bitbucket, or Azure DevOps is connected, or asks which imported repository records already exist. Read-only: returns provider status and browser-only connect/reconnect guidance without exposing credentials. Use repository-link tools for Space Autopilot links.

list-provider-connections

Use this when the user wants to choose a repository from a connected GitHub, GitLab, Bitbucket, or Azure DevOps provider before creating an Autopilot link. Read-only external-provider lookup: fetches repository choices or returns reauthorization/browser guidance. Requires provider and space_id.

list-provider-repositories

Use this when the user wants to browse a Space tree, list pages/docs/documents/folders, find numeric document or item IDs, or inspect structure before editing. Read-only: returns documents and folders for one numeric space_id without changing content.

list-space-documents

Use this when the user asks which repositories are linked to a Space for Autopilot, repo sync, suggestion generation, trigger events, or recent sync activity. Read-only: returns configured repository links plus bounded sync status/activity without exposing raw provider payloads.

list-space-repository-links

Use this when the user wants to review pending, snoozed, done, high-confidence, or filtered Autopilot/repository-sync documentation suggestions for a Space. Read-only: returns suggestion inbox items and IDs for later apply/discard/snooze tools without changing documents.

list-space-suggestions

Use this when the user asks to see, choose, or look up their documentation Spaces, especially before using tools that need a numeric space_id. Read-only: returns accessible Spaces and does not change settings or documents.

list-spaces