GitBook
Search and edit your GitBook spaces and published documentation. Sign in with GitBook to connect.
What GitBook exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the gitbook__ namespace. Your agent never loads them all — it searches, and gets the few that match.
gitbook__create_change_request3 arguments · 1 required
Opens a change request on a space. Published content is never edited directly: create a change request, edit pages within it, then submit/merge it. Returns the new change request id needed for those follow-ups. When the change request fixes a documentation issue found by GitBook, pass siteFindingId so merging it resolves the finding. See get_usage_guide("editing").
Required
spaceIdgitbook__describe_operation1 argument · 1 required
Describes one GitBook API operation found via search: its path/query parameters and request-body JSON Schema, so you can build params for invoke_operation. Read-only.
Required
operationIdgitbook__get_page3 arguments · 1 required
Returns a page's content as markdown plus its id, title and path. Look the page up by pageId or by path. Use it to read content before editing. Find a space with get_site_structure; to list that space's pages, use the operation surface — invoke_operation getSpaceById to read its `revision`, then getRevisionById to get the revision's pages.
Required
spaceIdgitbook__get_site_structure2 arguments · 2 required
Returns a site's navigation structure: its sections, groups, external links (with destination URLs), and published spaces, with the paths and ids needed to read content. Pass the organization id (the same one used with list_sites) and the site id. Use it to map a site before reading or editing. Find a site first with list_sites; read page content with get_page.
Required
organizationIdsiteIdgitbook__get_usage_guide1 argument
Returns procedural guidance for working with GitBook through this server (content model and step-by-step recipes). Call it when unsure how to orient, read, or edit content. Omit topic to list available topics.
gitbook__invoke_operation2 arguments · 1 required
Runs one GitBook API operation discovered via search, for capabilities not covered by a curated tool. Pass operationId and params (path/query/body). Returns the operation's JSON response, or a one-line status when the operation answers with no content. The surface includes operations that are visible to the public or cannot be undone (for example publishing a site or merging a change request), so confirm before invoking one.
Required
operationIdgitbook__list_site_topics2 arguments · 2 required
Lists the topics and subtopics a site's content and visitor questions are organised under, returning each one's label and id. Use it to resolve a topic by name, or to discover a topic id before filtering Ask AI questions, answers or stats by topic (the `topic` parameter of getSiteQuestionStats, listSiteQuestions and listSiteQuestionAnswers). Returns labels and ids only; use getSiteTopicById for a single topic's summary and question stats.
Required
organizationIdsiteIdgitbook__list_sites3 arguments · 1 required
Lists the published sites in a GitBook organization, the usual entry point for orientation. Returns each site's title, visibility, hostname and id. To reach site content, use this first to find a site, then get_site_structure to see the spaces (where content lives) within it. Not for listing a site's content directly (use get_site_structure).
Required
organizationIdgitbook__report_tool_feedback13 arguments · 2 required
Reports a problem you hit while using this server's tools or operations, or an improvement worth making, so they can be fixed. Use it the moment you run into friction: a confusing tool or parameter, a call that failed or returned something unusable, a task that took far more calls than it should have, or something you needed that no tool or operation could do. It also takes suggestions when nothing went wrong; there is no category for those yet, so pick the one the improvement is about. Report the tool or operation itself, not the content it returned. Reporting is cheap and does not affect your current task, so prefer reporting over staying silent; then carry on with what you were doing.
Required
categorysummarygitbook__search1 argument · 1 required
Searches the GitBook API operations this server can run, returning matches (id, method, path, summary) to run with invoke_operation. Use describe_operation for an operation's inputs. Use it to find operations beyond the curated tools. Read-only.
Required
querygitbook__submit_or_merge_change_request2 arguments · 2 required
Merges a change request, publishing its edits to the space. This is destructive and irreversible. Use it to finish the editing flow after create_change_request and editing pages via updateChangeRequestContent. Reports conflicts instead of merging when the change request is out of date.
Required
spaceIdchangeRequestId
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Switch GitBook on
Authorize it from your library; the grant is yours and stays yours.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
