GitBook MCP MCP server icon

GitBook MCP

by GitBook MCP

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Productivity9 tools

Create GitBook sites, open change requests and edit docs pages from an AI agent. 9 tools, OAuth; a change request is the write path.

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.

Connect GitBook MCP via MCP

https://mcp.gitbook.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect GitBook MCP once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

GitBook MCP Tools & Capabilities (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_operation is 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_request can 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

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.

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.

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.

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.

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.

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

Server Info

Category
Productivity
Developer
GitBook MCP
Tools
9
Domain
mcp.gitbook.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.

Ready to connect GitBook MCP?

Connect GitBook MCP once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.