Connect an AI assistant to DocuWriter

Connect your assistant to DocuWriter to search existing documentation, read complete pages, and work with Spaces without copying documents between applications. MCP is the connection protocol; your DocuWriter account remains the source of permissions and available resources.

Choose your client

Follow the guide for ChatGPT or Codex, Claude Code, Cursor, or VS Code. All use this remote endpoint:

https://app.docuwriter.ai/mcp

Sign in through the browser authorization screen when your client connects. You do not need to generate a DocuWriter API token or run a local DocuWriter MCP package. The REST API has a separate API-token setup.

Verify the connection with a read

Ask: “Use DocuWriter to list my Spaces with their IDs.” Choose the intended Space, then ask: “Search that Space for authentication and read the most relevant page.” A successful connection returns resources your account can access. An empty list can mean the authorized account has no Spaces; it does not necessarily mean the connection failed.

Use precise requests

For a change, identify the Space, page, desired result, and whether you want a proposal or an applied update. For example: “Read the deployment guide in Space 123, draft a rollback section, and show it to me before updating the page.” Replace example IDs with returned IDs.

The assistant can use supported generation and management tools, but repository authorization, initial repository selection, file upload, billing, and other browser steps still happen in DocuWriter. Connecting MCP alone does not import a repository or generate documentation. Start with the repository quickstart if your account has no documentation yet.

See the capability reference and approval behavior before using tools that change or share content.