Connect Cursor

Add DocuWriter to Cursor so your coding assistant can consult the same documentation your team maintains in Spaces.

Configure the server

Create or update .cursor/mcp.json in your project. Merge this entry into existing configuration rather than replacing other servers:

{
  "mcpServers": {
    "docuwriter": {
      "url": "https://app.docuwriter.ai/mcp"
    }
  }
}

For a connection across projects, use Cursor’s global MCP configuration instead. Open Cursor’s MCP settings, enable the server, and complete OAuth authorization in the browser. Each collaborator signs in with their own DocuWriter account; the shared configuration contains the endpoint, not their credentials. Cursor’s MCP documentation explains its configuration scopes.

Check access

Ask Cursor: “Use DocuWriter to list my Spaces and their IDs.” Choose the intended Space, then ask it to search for a specific subject and read the page. This verifies retrieval without creating new content.

Work from documentation while coding

Try: “Before changing authentication, read the authentication and API guides in Space 123. Explain the documented constraints and cite the pages.” After the code change, ask for a proposed documentation update and inspect it before saving.

For a request to create a page, include the destination Space and title. For an update, identify the existing page so the assistant does not create a duplicate. See MCP capabilities for tool families and browser-only steps.

If DocuWriter tools do not appear, check that the server is enabled, OAuth completed, and the current assistant mode supports tools. Refresh the connection after server capabilities change. A permission error on one Space can be an account-access issue even when the connection itself works.