gitbook-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITBOOK_API_TOKEN | Yes | GitBook API token | |
| GITBOOK_API_BASE_URL | No | API base URL (default: https://api.gitbook.com/v1) | |
| GITBOOK_DEFAULT_ORG_ID | No | Default organization ID | |
| GITBOOK_DEFAULT_SPACE_ID | No | Default space ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_spaceA | Get details of a GitBook space by its ID |
| update_spaceB | Update a GitBook space's properties (title, visibility, etc.) |
| create_spaceA | Create a new GitBook space in an organization |
| duplicate_spaceA | Duplicate an existing GitBook space (creates a full copy) |
| list_spacesB | List all spaces in a GitBook organization |
| search_space_contentB | Search for content within a GitBook space |
| get_space_revisionC | Get the full content tree of a GitBook space (or change request) |
| list_pagesB | List all pages in a GitBook space (or change request) |
| get_page_by_idA | Get a specific page by its ID from a GitBook space (or change request) |
| get_page_by_pathA | Get a specific page by its URL path from a GitBook space (or change request) |
| get_page_linksB | Get all outgoing links from a page |
| get_page_backlinksA | Get all pages that link to a specific page (backlinks) |
| list_filesA | List all files (images, attachments) in a GitBook space (or change request) |
| get_fileA | Get details and download URL for a specific file in a GitBook space |
| create_change_requestB | Create a new change request (similar to a PR/draft) in a GitBook space |
| list_change_requestsA | List change requests in a GitBook space |
| get_change_requestA | Get details of a specific change request |
| update_change_requestB | Update a change request's properties (subject, status, etc.) |
| merge_change_requestB | Merge a change request into the main content (DESTRUCTIVE: publishes changes) |
| sync_change_requestB | Sync/update a change request with the latest main content |
| list_reviewsA | List reviews on a change request |
| submit_reviewA | Submit a review on a change request (approve, request changes, or comment) |
| list_requested_reviewersB | List users who have been requested to review a change request |
| request_reviewersB | Request specific users to review a change request |
| remove_reviewerA | Remove a requested reviewer from a change request (DESTRUCTIVE) |
| list_commentsA | List comments on a GitBook space or change request |
| post_commentA | Post a new comment on a GitBook space or change request |
| update_commentA | Update an existing comment (uses PUT as per GitBook API) |
| delete_commentA | Delete a comment (DESTRUCTIVE: cannot be undone) |
| list_comment_repliesA | List replies to a specific comment |
| post_comment_replyA | Post a reply to an existing comment |
| git_importA | Import content from a Git repository into a GitBook space (DESTRUCTIVE: overwrites existing content) |
| git_exportB | Export GitBook space content to a Git repository |
| get_git_infoB | Get Git sync configuration and status for a GitBook space |
| get_organizationA | Get details of a GitBook organization |
| list_collectionsA | List all collections in a GitBook organization |
| get_collectionA | Get details of a specific collection in a GitBook organization |
| ask_aiB | Ask GitBook AI a question about the organization's documentation content |
| import_contentA | Import content into a GitBook organization from a URL (DESTRUCTIVE: may overwrite existing content depending on target) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
Most tools target distinct resource-action pairs, but a few overlaps exist: get_page_by_id vs get_page_by_path both retrieve pages, and git_import vs import_content both perform destructive imports from different sources. These are minor confusions, as the descriptions clarify the differences.
The naming convention is predominantly verb_noun in snake_case (e.g., get_space, create_change_request, list_comments), which is consistent. However, git_import and git_export break the pattern by placing the noun first, and ask_ai is slightly anomalous. Overall, the style is readable and predictable with only minor deviations.
With 39 tools, this server is heavily over-scoped for an MCP server. The domain of GitBook is broad, but the tool count exceeds the typical range and feels unwieldy. Many tools are narrowly focused (e.g., list_requested_reviewers vs remove_reviewer), and consolidation could reduce the count while maintaining functionality.
Significant gaps exist in page management: there are no tools to create, update, or delete pages directly. While change requests are well-covered, the inability to manage pages is a critical omission. Also missing are delete operations for spaces and change requests, limiting lifecycle completeness.