← Explore all mcp servers

DOCUMENTATION PUBLISHING / GitBook

GitBook MCP

GitBook's official hosted MCP at mcp.gitbook.com lets agents act on an organisation's content — create and configure sites, open change requests, draft and edit pages, restructure docs — over Streamable HTTP with OAuth browser sign-in or a personal access token. GitBook also auto-generates a read-only MCP server for every published docs site, inheriting the site's access model.

“GitBook exposes an MCP server that lets AI tools act on content in your organization.”

01 / THE REASONING

Why this made the selection.

  • GitBook operates a hosted MCP server for acting on organisation content and additionally auto-generates a read-only MCP server for every published docs site — two distinct publisher-maintained surfaces.
  • The transport statement is explicit and honest: Streamable HTTP only, with stdio and SSE named as unsupported, so client compatibility can be judged before connecting.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • GitBook MCP documentation: the endpoint is https://mcp.gitbook.com/mcp; clients connect with OAuth browser sign-in or a personal access token as a Bearer header; tools create and configure sites, open change requests, draft content, edit pages and restructure docs; official plugins exist for Claude, ChatGPT and Cursor; Streamable HTTP only — stdio and SSE explicitly unsupported.
  • MCP servers for published docs documentation: every published site gets an MCP server at {docs-site-url}/~gitbook/mcp, read-only, inheriting the site's authentication including share links and the /~gitbook/mcp/auth variant for authenticated sites.

Our findings

  • The server is remote-only; there is no repository, package or revision to pin.
  • The write surface is scoped to documentation workflows on the organisations the signed-in user can access.
  • Correction, 2026-10-13: the earlier configExample matched no printed block, and compatibility named Claude Code and Codex as plugin clients. The page’s plugins are for Claude, ChatGPT and Cursor. The configExample is now its VS Code .vscode/mcp.json block.

Not established by this review

  • No GitBook organisation was connected and no change request was created.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude mcp add --transport http gitbook https://mcp.gitbook.com/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Add the server to the MCP client at https://mcp.gitbook.com/mcp, or install the official plugin for Claude, ChatGPT or Cursor.
  2. Complete the browser sign-in, or pass a personal access token as an Authorization Bearer header.
  3. For a published docs site's read-only server, use {docs-site-url}/~gitbook/mcp instead.

Before you start

  • A GitBook account with access to the target organisation, or a published docs site for the read-only server.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "servers": {
    "gitbook": {
      "type": "http",
      "url": "https://mcp.gitbook.com/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://gitbook.com/docs/docs-as-code/gitbook-mcp

    Supports: summary, upstreamDescription, homepage, descriptionSourceUrl, install, configExample, compatibility, transports, whySelected, access

  2. https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs

    Supports: bestFor, limitations

Evidence & Ask