GitBook Docs MCP server

Tools provided by GitBook Docs 4

Some details were sanitized for public display.

• askQuestionNo outputSchema

  Ask a natural-language question about GitBook Documentation and get a synthesized answer, with links to the source pages. Prefer this over `searchDocumentation` when you want a direct answer to a question rather than a list of matching pages; use `searchDocumentation`/`getPage` when you need to browse or read full pages yourself.

  Input goal?: string, question: string

  • goal?: stringoptional

    The broader end goal you are ultimately trying to accomplish (as/on behalf of the user). Used to tailor the answer to be most useful for your goal. Optional.

  • question: stringrequired

    The natural-language question to answer about GitBook Documentation.

• getPageNo outputSchema

  Fetch the full markdown content of a specific documentation page from GitBook Documentation. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. [REDACTED URI] Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

  Input url: string

  • url: stringrequired

    The URL of the page to fetch

• searchDocumentationNo outputSchema

  Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about GitBook Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

  Input query: string

  • query: stringrequired
• sendFeedbackNo outputSchema

  Report an issue in the documentation of GitBook Documentation so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm

  Input content: string, goal?: string, pageUrl: string

  • content: stringrequired

    Explain the issue in full, as if writing to a documentation maintainer who never saw this conversation. Describe what is wrong, where on the page it appears (quote the exact sentence or section title when possible), what the user was trying to do, and, when relevant, what the correct or expected information should be. Write a few clear, specific sentences in English. Never include personal or confidential information from the conversation. Up to 2048 characters.

  • goal?: stringoptional

    The broader end goal you were ultimately trying to accomplish (as/on behalf of the user) when you hit this issue. Gives the team the context you were working towards. Optional.

  • pageUrl: stringrequired

    The full URL of the page the issue is about (e.g. [REDACTED URI] so the finding is linked to the exact page.