6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
GitBook MCP
Create GitBook sites, open change requests and edit docs pages from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the GitBook MCP connector does
The GitBook MCP server connects a GitBook organization to Claude and any MCP-compatible agent. Its 9 tools search and read pages, inspect site structure, create and configure sites, and edit content — with writes flowing through GitBook's change-request review model rather than straight onto a page.
Connection verified
Connection checked by Agentman on .
Listed in Anthropic’s Connectors Directory at community tier — a listing, not a partner-level review.
Anthropic states this reflects the level of review a connector received, not a security audit.
GitBook MCP tools (9)
- create_change_request
- describe_operation
- get_page
- get_site_structure
- get_usage_guide
- invoke_operation
- list_sites
- search
- submit_or_merge_change_request
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
invoke_operationis a generic API passthrough, so the reachable surface is wider than the other eight tools imply.- This is the organization-level server, not the read-only one GitBook generates for published sites — it can create and configure sites.
- Change requests still merge.
submit_or_merge_change_requestcan land a change, so the review step protects you only if a human is the one merging. - GitBook publishes no rate limits for the MCP server that we could find, so none are stated here.
- We did not read tool schemas. The endpoint requires OAuth, so names come from Anthropic's directory and behaviour from GitBook's documentation. We exercised no tool.
Frequently asked questions
How does the GitBook MCP server write content?
Through change requests rather than direct edits. The tool set pairs create_change_request with submit_or_merge_change_request, which is GitBook's own review flow — an agent proposes changes in a branch-like container and a separate call submits or merges it. That gives you a reviewable diff instead of silent edits to a live page.
Why does the GitBook MCP server have a describe_operation tool?
Because it is partly a dispatcher. Alongside named tools like get_page and search, GitBook exposes describe_operation and invoke_operation, which let an agent discover and call API operations that have no dedicated tool. get_usage_guide returns GitBook's own instructions for the server, so the agent can read the intended workflow first.
Can I use the GitBook MCP server read-only?
Not this one, but GitBook publishes a separate read-only server for published docs sites. GitBook states it creates one automatically for a published site, documented under MCP servers for published docs. The server at mcp.gitbook.com is the organization-level one and includes site creation and content editing.
Do I need an API token for the GitBook MCP server?
No, OAuth is the documented default. GitBook's Claude Code instructions have you add the server then run the slash mcp command to finish a browser sign-in, and we confirmed the server issues an OAuth challenge naming oauth.gitbook.com as its authorization server. A personal access token is documented as an alternative for clients that prefer one.
Which clients can connect to the GitBook MCP server?
GitBook publishes official plugins for Claude, ChatGPT and Cursor, and documents terminal setup for Claude Code with a single claude mcp add command. It also names Codex and describes the server as usable by other MCP clients generally, so any client that supports remote MCP over OAuth should connect.
Why does the GitBook MCP URL show an error in my browser?
Because it is an MCP endpoint, not a web page. GitBook notes explicitly that opening the URL in a browser returns an error and that it must be used in an MCP client capable of making the protocol's HTTP requests. Seeing that error is not a sign the server is down.
Sources
- GitBook MCP documentation (read as Markdown via the
.mdvariant; retrieved 2026-09-13). Note the URL Anthropic's directory publishes,gitbook.com/docs/getting-started/ai-documentation/gitbook-mcp, redirects here; the canonical slug is cited above. · retrieved 2026-09-13 - Live OAuth posture check against
https://mcp.gitbook.com/mcp— HTTP 401 with awww-authenticateBearer challenge, and RFC 9728 metadata athttps://mcp.gitbook.com/.well-known/oauth-protected-resourcenaminghttps://oauth.gitbook.comas the authorization server (2026-09-13) · retrieved 2026-09-13 - Anthropic Connectors Directory entry (retrieved 2026-09-13) · retrieved 2026-09-13
- GitBook support — <support@gitbook.com> · Policies
More Productivity connectors
Adobe Experience Manager
Create, edit, publish and delete AEM pages, content fragments and assets from an agent.
Adobe Workfront
Find, create, update and delete Workfront work items from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put GitBook MCP to work.
Connect GitBook MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.