GitBook

What you can ask

• Turn my markdown folder into a GitBook docs siteCopy

  Example path list_site_topics→get_site_structure · Configure site skill

• Update the docs for this page and open a change request for review
• Publish my OpenAPI spec as interactive API reference docs

MCP connector

Server URL

https://mcp.gitbook.com/mcpCopy

Login

OAuth

Tools

Skills

6 in the ChatGPT listing

• Build integrationBuild, develop, and publish GitBook integrations — apps that run inside GitBook to add custom blocks, react to events, connect external services via OAuth, and extend the editor.
• Configure siteCreate and maintain entire GitBook documentation sites end-to-end — design the site structure from source content, scaffold a Git repository in monorepo layout, set up the GitHub/GitLab remote, drive the GitBook API (via its REST API or MCP server) to create the site/sections/spaces, apply branded customization, and hand the user clean instructions for the one UI step (Git Sync wiring) that GitBook does not expose programmatically.
• Cr createDrive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new page), request reviewers, notify Slack, then pull review comments back in, fix them, re-push, and resolve.
• Cr reviewReview GitBook change requests from Claude Code by calling the GitBook REST API directly with curl (no CLI) — the reviewer-side companion to cr-create (the authoring side over the same API).
• Write docsWrite, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor.
• Write openapiAuthor, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook.