Summary
Documentation you can query, rather than documentation somebody has to go and read.
The read-only shape fits the main use exactly: letting an agent answer from the docs your team already wrote, with search scoped to a space and retrieval by the path a human would quote at you. Nothing writes back, so a correction discovered this way still has to be made in GitBook by hand.
What it is
A read-side server over the GitBook API with 12 tools across organizations, collections, spaces, pages and uploaded files.
What you get
- The organizations an API token can reach, and the spaces and collections beneath them
- A space's complete content structure and page hierarchy
- Page content by page id or by path, with format and metadata options
- Text search within a space
- Files uploaded to a space, listed and then inspected individually
- Collections resolved to the spaces that belong to them
Requirements
GITBOOK_API_TOKEN, and the organization you intend to work in — the organization listing shows which ones that token reaches, and most calls take an organizationId or a spaceId.
Setup effort
One command plus a key — npx gitbook-mcp, then supply credentials