Gitbook MCP
Manage your docs from the AI tools your team already uses
Connect Claude, ChatGPT, Cursor, or any MCP client to GitBook. Your agents can create sites, draft pages, and restructure docs, and every change goes to your team for review before it’s published.
Give your agents real access to your docs
GitBook MCP lets AI tools act on content in your organization using GitBook’s API
FEATURES
Your agents do the work.
Your team has the final say.
GitBook MCP fits into your existing review workflow,
so speed doesn’t cost you control
Change requests
Every edit lands where your team can review it
Your agent will always work in a branch, so nothing goes live until your team approves and merges. You get a preview link to check every draft.
Any AI client
Install the official plugin, or point any MCP client at a single endpoint. GitBook is where the docs end up, without your team switching tools.
FAQs
What is GitBook MCP?
GitBook MCP is a server that connects AI tools like Claude, ChatGPT, and Cursor to your GitBook organization. Once it’s connected, you can ask your AI tool to create docs sites, open change requests, draft pages, edit content, and restructure your docs. It uses the GitBook API, so everything it does shows up in GitBook just like changes your team makes.
How is GitBook MCP different from the MCP server for published docs?
GitBook MCP is for your team. Published docs MCP is for your readers.
GitBook MCP gives your team’s agents access to your organization so they can edit and manage documentation. GitBook creates a published docs MCP server automatically for every published site. It’s read-only, and it lets AI tools answer questions from your public content. Most teams use both.
Which AI tools work with GitBook MCP?
There are official plugins for Claude, ChatGPT, and Cursor, and each installs in a click. VS Code and any other MCP client can connect by pointing to https://mcp.gitbook.com/mcp. GitBook MCP uses streamable HTTP, and it doesn’t support stdio or SSE.
Can GitBook MCP publish changes directly?
Yes, but only if you directly ask it to and you have permission to publish. By default, your agent will work in a change request, and you’ll get a preview link to check the work before merging. Nothing will go live until someone on your team reviews and manually merges, or you ask your agent to merge it for you.
Can an agent access more than I can?
No. GitBook MCP acts with your personal GitBook identity, whether you connect through OAuth sign-in or a personal access token. Every action follows your role and permissions, so an agent can’t read, edit, or publish anything you couldn’t yourself. There’s no separate access model to set up or audit.
Do I need to be a developer to use GitBook MCP?
No. If your team uses Claude or ChatGPT, you can install the GitBook plugin, sign in, and describe what you want in plain language. Developers can also connect from Cursor, VS Code, or the command line if that’s where they work.
How does GitBook MCP work with GitBook Agent?
They do the same kind of work from different places. GitBook Agent works inside GitBook and in channels like Slack, GitHub, and Linear, where it can suggest updates based on user signals. GitBook MCP brings GitBook into the AI tools your team already uses. Both follow the same review workflow, so changes go into change requests your team can approve, no matter which one you use.
