What can you do with the GitBook integration?

LiveContext exposes 28 operations on GitBook, covering space, change request, page and answer. Common uses include reading page content, auditing space assets and checking Git sync status.

LiveContext

All integrations

GitBook integration

Documentation platform API for managing spaces, pages, content, and collaboration. Create and manage documentation spaces, organize content with pages and collections, search across documentation, handle change requests and revisions, manage organization members, and integrate with Git repositories. Perfect for building documentation workflows, content management systems, knowledge base integrations, and team collaboration tools.

28 toolsTokenAPI docs

Connect GitBook How integrations work

Common GitBook use cases

reading page content
auditing space assets
checking Git sync status
verifying authentication
building navigation menus
reviewing pending changes
building member selector UI
publishing reviewed changes
cross-space knowledge queries
renaming documentation spaces

What you can do with GitBook

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Space, 6 operations

DELETEdelete_space
Deletes a GitBook space. The space is moved to trash and can be restored within 7 days using the restore endpoint. Requires admin permissions on the space.
POSTduplicate_space
Creates a duplicate copy of an existing GitBook space with all its content. Returns the newly created space object with a new ID.
GETget_space
Retrieves details about a GitBook space including title, visibility settings, and metadata. Returns space configuration, edit mode, and parent organization. Essential for understanding space context before content operations.
GETlist_collection_spaces
Lists all spaces within a GitBook collection. Returns space objects with IDs, titles, and metadata. Essential for navigating collection contents.
GETlist_organization_spaces
Lists all spaces in a GitBook organization accessible to the authenticated user. Returns space IDs, titles, visibility, edit mode, and URLs. Supports pagination and title filtering.
PATCHupdate_space
Updates properties of a GitBook space including title, emoji, icon, edit mode, default access level, and language. Modify space settings without affecting content. Returns the updated space object.

Change request, 5 operations

POSTcreate_change_request
Creates a new change request to propose content modifications to a GitBook space. Provide a subject title. Returns the new change request with its ID for subsequent content modifications.
GETget_change_request
Retrieves details about a specific change request including status, subject, description, author, and timestamps. Essential for reviewing proposed documentation changes.
GETlist_change_requests
Lists change requests (draft content revisions) for a GitBook space. Returns change request IDs, subjects, status (draft, open, archived, merged), and author information. Supports filtering and pagination.
POSTmerge_change_request
Merges a change request to apply its content modifications to the main space revision. Closes the change request after successful merge. Requires appropriate permissions on the space.
PATCHupdate_change_request
Updates properties of an existing change request including subject, description, and status. Allows modifying change request metadata without affecting content.

Page, 5 operations

GETget_page_by_id
Retrieves a specific page from a GitBook space by its ID. Returns page metadata, content in requested format (markdown or document), and page configuration. Essential for reading documentation content.
GETget_page_by_path
Retrieves a page from a GitBook space by its URL path. Returns page metadata and content using the page's slug path. Useful when you know the URL but not the page ID.
GETlist_space_pages
Lists all pages in a GitBook space with their hierarchy. Returns page IDs, titles, paths, and parent-child relationships. Essential for understanding documentation structure.
GETsearch_organization_content
Searches content across all spaces in a GitBook organization. Returns matching pages grouped by space with titles, paths, and content snippets. Enables cross-space documentation search.
GETsearch_space_content
Searches content within a GitBook space. Returns matching pages with titles, paths, and content snippets highlighting matches. Essential for finding specific information in documentation.

Answer, 2 operations

POSTask_organization
Asks a question across all accessible spaces in a GitBook organization using AI. Returns an AI-generated answer with source references from across the organization's documentation.
POSTask_site
Asks a question about site content using GitBook's AI. Provide a question and optional scope/context. Returns an AI-generated answer synthesized from the documentation with source references.

Organization, 2 operations

GETget_organization
Retrieves details about a GitBook organization including name, settings, and metadata. Returns organization configuration, plan type, and member counts. Essential for understanding organization context.
GETlist_organizations
Lists all organizations accessible to the currently authenticated user. Returns organization objects with IDs, titles, and metadata. Essential for multi-org workflows.

Site, 2 operations

GETget_site
Retrieves details about a specific docs site including title, visibility, hostname, and configuration. Essential for managing published documentation portals.
GETlist_sites
Lists all published docs sites in a GitBook organization. Returns site objects with IDs, titles, visibility settings, and published status. Supports filtering by title and published status.

User, 2 operations

GETget_current_user
Returns details about the user associated with the current authentication token. Includes user ID, display name, email, and avatar URL. Essential for identifying the authenticated user in integrations.
GETget_user
Retrieves public profile information for a GitBook user by their ID. Returns display name, avatar URL, and public profile details. Use to display user information in external applications.

Collection, 1 operation

GETget_collection
Retrieves details about a GitBook collection including title, description, and contained spaces. Collections group related documentation spaces for organization and navigation.

File, 1 operation

GETlist_space_files
Lists all files (images, attachments, assets) in a GitBook space. Returns file IDs, names, content types, sizes, and URLs. Essential for managing documentation assets.

Git, 1 operation

GETget_space_git_info
Retrieves Git synchronization configuration for a GitBook space. Returns repository URL, branch name, sync direction, and current sync status. Essential for Git-integrated documentation workflows.

Member, 1 operation

GETlist_organization_members
Lists all members of a GitBook organization with their roles and permissions. Returns user IDs, display names, roles, and join dates. Supports pagination, role filtering, and name/email search.

Use GitBook from Claude Code, Cursor or Codex

Connect GitBook in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its GitBook operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect GitBook

Create your workspace
Sign up free. Nothing to install.
Connect GitBook once
Add your GitBook connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

GitBook integration FAQ

What can you do with the GitBook integration?: LiveContext exposes 28 operations on GitBook, covering space, change request, page and answer. Common uses include reading page content, auditing space assets and checking Git sync status.