GitBookNot published by vendorVerified 2026-10-17

GitBook MCP server for Claude & Cursor

Add {docs-site-url}/~gitbook/mcp to Claude, Cursor or Codex and the agent can search and read that product’s docs. Keyless for public sites.

Verified factsChecked 2026-10-17

PriceFree to connect for readers. GitBook includes the MCP server with every published docs site.1 [Verified 2026-10-17]
API key / authNone for public sites. Fully authenticated sites use OAuth with Dynamic Client Registration through the site’s auth provider; partially authenticated sites use /~gitbook/mcp/auth.1 [Verified 2026-10-17]
Rate limitNo limit is published, and our test responses carried no rate-limit headers. Treat it as a shared public service and keep calls modest.1 [Verified 2026-10-17]
TermsGitBook’s terms of service apply to the platform; the documentation content belongs to each site’s owner.2 [Verified 2026-10-17]
AvailabilityOnly works when the site owner leaves Page actions enabled. If they turn it off, /~gitbook/mcp returns 404.1 [Verified 2026-10-17]
Toolstools/list on GitBook’s own docs MCP returned searchDocumentation, getPage, askQuestion and sendFeedback (the endpoint accepts POST only, so opening it in a browser errors).1 [Verified 2026-10-17]
Markdown and llms.txtAppend .md to any published page for Markdown; /llms.txt and /llms-full.txt are published at the site root.3 [Verified 2026-10-17]

FeaturesChecked 2026-10-17

YesNoN/ANot published
CapabilityValueNote
StatusThe docs describe it as included with every published site, with no stage label.Not published1 [Not published by vendor: checked 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]The docs describe it as included with every published site, with no stage label.
API key requiredNone for public sites. Authenticated sites use OAuth through the site’s auth provider.No1 [Verified 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]None for public sites. Authenticated sites use OAuth through the site’s auth provider.
Free tierIncluded with every published site. Free to connect for readers.Yes1 [Verified 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]Included with every published site. Free to connect for readers.
Rate limitNo limit is published, and our test responses carried no rate-limit headers.Not published1 [Not published by vendor: checked 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]No limit is published, and our test responses carried no rate-limit headers.
Official MCP serverPer site, /~gitbook/mcp. Read-only access to the latest published content.Yes1 [Verified 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]Per site, /~gitbook/mcp. Read-only access to the latest published content.
Official SDKGitBook’s @gitbook/api client targets the GitBook management API, not the per-site docs MCP.N/A4 [Verified 2026-10-17 on https://www.npmjs.com/package/@gitbook/api]GitBook’s @gitbook/api client targets the GitBook management API, not the per-site docs MCP.
Data license / termsGitBook’s platform terms apply; the content belongs to each site’s owner.Owned by each docs site2 [Verified 2026-10-17 on https://gitbook.com/docs/policies/terms]GitBook’s platform terms apply; the content belongs to each site’s owner.
Commercial use allowedDepends on each docs site’s owner; GitBook publishes no rule for readers.Not published1 [Not published by vendor: checked 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]Depends on each docs site’s owner; GitBook publishes no rule for readers.
CORS / browser usePreflight had no CORS headers. OPTIONS returned 204 without Access-Control-Allow-Origin.No5 [Verified 2026-10-17 by test request to https://gitbook.com/docs/~gitbook/mcp]Preflight had no CORS headers. OPTIONS returned 204 without Access-Control-Allow-Origin.
Freshness / coverageDrafts and unpublished changes stay private.Latest published version only1 [Verified 2026-10-17 on https://gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md]Drafts and unpublished changes stay private.

What it does

GitBook automatically runs a Model Context Protocol server for every published docs site. Point an MCP client at the site URL plus /~gitbook/mcp and the agent gets read-only tools to search the docs, fetch a full page as Markdown and ask a question against them. Because many developer products host their docs on GitBook, this is a quick way to stop a coding agent from guessing at an API: connect the vendor’s docs and let it look things up. The same sites also serve any page as Markdown when you add .md to its URL.

Working exampleRun 2026-10-17

curl -sS -X POST "https://gitbook.com/docs/~gitbook/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"searchDocumentation","arguments":{"query":"custom domain"}}}'

Response (trimmed)

HTTP 200 (text/event-stream)
event: message
data: {"result":{"content":[{"type":"text","text":"Title: Set a custom domain
  Link: https://gitbook.com/docs/publish/custom-domain
  Content: Navigate to the site for which you want to set the custom domain. ..."}, ...]}}

Agent setup

Prompt to give your agent

I’ve connected the vendor’s docs as the MCP server "vendor-docs". Before writing any code against their API, use searchDocumentation to find the relevant pages and getPage to read them in full. Quote the exact parameter names and limits you rely on with the page link, and tell me if the docs don’t cover something instead of guessing.

Agent / MCP-style tool snippet

// Cursor .cursor/mcp.json (swap in any GitBook-hosted docs URL)
{
  "mcpServers": {
    "vendor-docs": { "url": "https://gitbook.com/docs/~gitbook/mcp" }
  }
}
// Claude Code:
// claude mcp add --transport http vendor-docs https://gitbook.com/docs/~gitbook/mcp
// Codex:
// codex mcp add vendor-docs https://gitbook.com/docs/~gitbook/mcp

Fit and safety

Good for

  • Letting a coding agent read a vendor’s API docs before writing integration code
  • Support bots that answer from your own published GitBook docs
  • Checking exact parameter names and limits instead of relying on model memory

Watch out

  • Do not assume every docs site has it. It only exists on GitBook-hosted sites with Page actions enabled; other sites return 404.
  • Do not use it for docs that need static visitor tokens in headers. GitBook says MCP auth does not support that setup.
  • Do not connect a dozen docs servers at once. Each adds tools to the agent’s context; connect the one or two you need for the task.
  • Do not treat askQuestion answers as the source of truth. Have the agent read the page with getPage and cite it.

Alternatives

You.com MCP (free)Keyless web search when the docs aren’t on GitBook or you need the wider web.
Wikipedia REST APIFree encyclopedia summaries for general background rather than product docs.
DexPaprika MCPAnother keyless hosted MCP server, for live DEX market data.

FAQ

Does GitBook have an MCP server?

Yes. Every published GitBook docs site has one at its site URL plus /~gitbook/mcp, for example https://gitbook.com/docs/~gitbook/mcp.

Do I need an API key for a GitBook docs MCP?

Not for public docs sites. Authenticated sites sign you in through OAuth using the site’s own auth provider.

How do I add GitBook docs to Cursor?

Add an entry to .cursor/mcp.json with "url": "{docs-site-url}/~gitbook/mcp", or add it in Cursor’s MCP settings.

Compare

Put GitBook docs MCP (per-site) side by side with other free agent tools on keys, limits, MCP support, licensing and CORS. Open the comparison grid →

SourcesFootnotes