GitBook MCP server

What the model can do

GitBook: your organizations and their spaces, a space's page tree, any page's markdown, and full-text search across a space or a whole organization; when you ask, can open a change request, add, edit or delete pages in it, review, request reviewers on, retitle, archive and merge it, comment on a space or change request, reply to comments, and duplicate a space.

Reads

• gitbook_meWho the GitBook token belongs to and the organizations they are a member of (id, title, plan).
• gitbook_spacesThe spaces (docs sites, wikis, books) in a GitBook organization: id, title, visibility, when last updated, open change requests…
• gitbook_pagesThe page tree of a GitBook space as its sidebar shows it: every page with its title, path, type (document, group, link), depth, description and link…
• gitbook_pageOne GitBook page as markdown, by page id or by its path within the space (as gitbook_pages shows it): title, path, description…
• gitbook_searchFull-text search in GitBook: within one space, or across every space of an organization.

Acts, when you ask

These change something in GitBook. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• gitbook_create_change_requestOpens a change request in a GitBook space under the token's user: a private branch of the space where pages can be added…
• gitbook_edit_change_requestChanges pages inside an open GitBook change request, all at once or not at all: insert a new page (markdown), update a page's markdown or title…
• gitbook_update_change_requestRetitles a GitBook change request or sets its status: draft, open (ready for review) or archived (closed without merging, which can be reopened).
• gitbook_merge_change_requestMerges a GitBook change request into the live space, so its edits are what every reader of the space (and its published site) sees.
• gitbook_review_change_requestSubmits a review on a GitBook change request as the token's user: approved or changes-requested, with an optional comment.
• gitbook_request_reviewersAsks the named organization members to review a GitBook change request; GitBook notifies each of them.
• gitbook_comment_on_change_requestPosts a comment (markdown) on a GitBook change request as the token's user, optionally on one page of it…
• gitbook_comment_on_spacePosts a comment (markdown) on a GitBook space, optionally on one of its pages, as the token's user; everyone with access to the space sees it.
• gitbook_reply_to_commentReplies (markdown) to a comment in a GitBook space as the token's user; the comment's author and thread see it.
• gitbook_duplicate_spaceMakes a copy of a GitBook space (its content) in the same organization, visible to whoever can see the organization's spaces.

Connect it

First connect GitBook on Dashboard → Connections, then add Memtro to your client once. The GitBook tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared GitBook connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Where in our docs do we explain webhook retries?
• › Read the 'Getting started → Install' page from the Developer docs space
• › Which spaces in the organisation have open change requests?
• › What does the API reference say about rate limits?
• › Open a change request fixing the rate limit on the API reference page to 600 a minute

Questions

Is this an official GitBook MCP server?

No. It is Memtro's MCP server with Memtro's GitBook connector behind it: the connector reads GitBook through its API with the credentials you connect on Dashboard → Connections, and GitBook publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in GitBook?

Only when you ask, and only what it has been granted: open a change request in a space; add, edit or delete pages inside a change request; retitle a change request, or set it to draft, open or archived; merge a change request into the live space; approve or request changes on a change request; ask named members to review a change request; comment on a change request; comment on a space or one of its pages; reply to a comment; duplicate a space. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Documents and wikis

• Google Drive MCP server
• Notion MCP server
• Confluence MCP server
• SharePoint and OneDrive MCP server
• Guru MCP server
• Dropbox MCP server