get_collection
Get detailed information about a specific GitBook collection
Read a GitBook workspace from the conversation: walk a space's page hierarchy, pull a page by id or by the path someone quoted, and search inside it for the passage that answers the question.
LABSCO SUMMARY
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.
A read-side server over the GitBook API with 12 tools across organizations, collections, spaces, pages and uploaded files.
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.
One command plus a key — npx gitbook-mcp, then supply credentials
USE CASES
Find the space the answer would live in, search inside it for the phrasing the customer used, then pull the page so the reply quotes what the docs actually say.
A shared link gives you a path, not a page id — fetch by path directly instead of walking the hierarchy to work out which page it refers to.
Start from the organizations the token reaches, expand the collections into their spaces, and read one space's structure to see how the documentation is arranged before reading any of it.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_collectionGet detailed information about a specific GitBook collection
get_collection_spacesList all spaces that belong to a specific GitBook collection
get_fileGet detailed information about a specific file uploaded to a GitBook space
get_page_by_pathRetrieve a page from a GitBook space using its path instead of page ID
get_page_contentRetrieve the content of a specific page from a GitBook space, with options for format and metadata
get_spaceGet detailed information about a specific GitBook space
get_space_contentGet the complete content structure and page hierarchy of a GitBook space
get_space_filesList all files (images, documents, etc.) uploaded to a GitBook space
list_collectionsList all collections in a GitBook organization, optionally filtered by organization ID
list_organizationsList all GitBook organizations accessible with the current API token
list_spacesList all spaces in a GitBook organization, optionally filtered by organization ID
search_contentSearch for content within a GitBook space using a text query
BEFORE YOU INSTALL
12 tools when we connected. Every tool is read-only; nothing creates, edits or publishes a page. The 6 prompts are separate and are not tools.
All 3 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx gitbook-mcp{
"servers": {
"gitbook-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"gitbook-mcp",
"--organization-id=<YOUR_ORGANIZATION_ID>"
],
"env": {
"GITBOOK_API_TOKEN": "<YOUR_GITBOOK_API_TOKEN>"
}
}
}
}{
"mcpServers": {
"gitbook-mcp": {
"command": "npx",
"args": [
"gitbook-mcp",
"--organization-id=<YOUR_ORGANIZATION_ID>"
],
"env": {
"GITBOOK_API_TOKEN": "<YOUR_GITBOOK_API_TOKEN>"
}
}
}
}{
"servers": {
"gitbook-mcp": {
"command": "npx",
"args": [
"gitbook-mcp",
"--organization-id=<YOUR_ORGANIZATION_ID>"
],
"env": {
"GITBOOK_API_TOKEN": "<YOUR_GITBOOK_API_TOKEN>"
}
}
}
}