Skip to main content
Doctorine

MCP

A safe way for agents to understand and improve your developer experience.

Expose published documentation for agent discovery, then give authenticated workspace agents scoped, change-first editing with OAuth, policy, revision checks, and audit history.

Start free Compare the trust modes
Workspace MCP OAuth connected
Agent Claude Code
Policy Docs editor
Change chg_auth-guide
  1. docs.searchFound “Authentication”read
  2. changes.stage_pageUpdated token scopesallowed
  3. changes.previewImmutable preview builtaudited

Give each agent only the access its job needs.

Published discovery and authenticated workspace action stay separate, with explicit policy at every tool call.

  • Published-content MCP on eligible public portals

  • Policy-aware workspace changes and publishing

  • OAuth, ReBAC, rate limits, and audit entries

Reading a release and changing a workspace are different trust decisions.

Doctorine keeps them as separate surfaces so public discovery never inherits private editing authority.

Public reader MCP

Served from an eligible public documentation portal and pinned to its active release.

  • Search published documentation
  • Read canonical pages
  • Discover pages and API endpoints
  • Access published resources
  • Submit feedback for review when enabled
Published content · optional reviewed feedback · no workspace edits

Authenticated workspace MCP

Connected through OAuth to a tenant, project, role, and explicit workspace policy.

  • Propose and stage page changes
  • Create, update, move, or delete pages
  • Inspect the isolated change and preview
  • Publish when policy allows
Scoped writes · revision checked · audited

Every action passes through project policy.

By default, agent edits are staged in an isolated change. A project may allow selected roles to apply or publish directly. Every path rechecks permissions and the base revision, then records the action.

  1. 01

    Authenticate

    OAuth resolves the user, tenant, project, and role.

  2. 02

    Authorize

    ReBAC and live-edit policy filter the catalog and the action.

  3. 03

    Choose the allowed path

    Suggest-only policy stages a change; approved roles can apply or publish directly.

  4. 04

    Recheck and record

    The base revision and permission are checked again before the action is audited.

CLI-assisted setup for the clients your team uses.

Doctorine uses a client’s own command when available, safely updates supported config formats, and hands back an explicit manual step when it cannot preserve the file.

  • Claude Code CLI-managed setup
  • Cursor CLI-managed config
  • Windsurf CLI-managed config
  • Gemini CLI CLI-managed setup
  • Codex CLI-managed setup
  • VS Code (Copilot) Workspace config
  • Zed CLI-assisted config
  • Cline CLI-managed config
  • OpenCode CLI-managed config
  • Grok CLI CLI-managed setup
  • Kimi CLI-managed config
  • Claude Desktop Manual connector

Need an MCP server for your own API?

The Doctorine CLI can generate a runnable MCP package locally from the released API model. That artifact is distinct from the hosted Doctorine workspace connector. 

❯ doctorine sdk generate --target mcp
Wrote dist/payments-api-mcp/
  package.json
  src/server.ts
  src/tools/
  README.md

Agent access remains part of the platform.

Identity, tenant scope, project policy, revisions, rate limits, and audit history travel with every action.

  • Published portal

    Eligible public portals expose published search, canonical page reads, endpoint discovery, and optional reviewed feedback without workspace editing authority.

  • Workspace MCP

    OAuth-authenticated agents act within ReBAC and project policy. The default path stages changes; selected roles may be allowed to apply or publish directly.

  • CLI setup

    Install the remote workspace connector into supported clients, or generate a separate runnable MCP server package for your own API.

Access is scoped at every tool call.

The operating boundary is visible in the tool catalog, authorization path, revision check, and recorded outcome.

Policy-aware writes
Agent edits default to an isolated change. Projects may allow selected roles to apply or publish directly; every path rechecks the base revision and permissions.
Policy on every action
OAuth identity, tenant isolation, ReBAC, live-edit policy, rate limits, and audit entries are applied at the tool boundary.
Narrow administration scope
Workspace MCP controls documentation and its release-change workflow—not billing, domains, membership, or SDK configuration.

Give agents useful access without giving away the workspace.

Publish discoverable documentation first, then enable authenticated change tools for the projects and roles that need them.

Set up Doctorine MCP