Kiwi
Kiwi

Kiwi for GitBook

Have the agent on a Kiwi step open a GitBook change request that documents its change, through GitBook's MCP server.

  • Your agent works in GitBook through its own connection. Kiwi does not call GitBook and never holds its credentials.
  • A workflow skill can list GitBook among the tools it requires. When you supply your agent's available tools to a skill check and GitBook is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to GitBook, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its GitBook connection, with report_configuration.
  • The agent submits links to its work in GitBook as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in GitBook

  • Open a change request and draft content in it.
  • Edit pages, and move, rename or restructure pages across a site.
  • Create and configure a new docs site.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to GitBook

    Add the GitBook MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.gitbook.com/mcp

    GitBook documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists GitBook among its required tools.

    Read the merged pull request and the docs site named in the assignment.
Open a GitBook change request and update the pages the change affects.
Move or rename pages only when the change makes the old structure wrong.
Submit the change request URL as the step's outputs.
Merging the change request is for the docs reviewer named in the assignment.
If the site is not in your organization, call report_blocker with its name.
Get startedRead the setup guide