Integration · Automate and collaborate

GitBook and Meteor AI agents

Connect GitBook to a Met: review your documentation's structure and propose changes in a change request for your team to review.

Book a demo See every integration

How does GitBook connect to Meteor?

With the GitBook ready connector, your Met works on the documentation or help center your company keeps in GitBook, using the account the admin authorizes. It lists the organization's sites, reads one site's page structure and opens a change request to propose a change without touching what is published; then it submits it for review or merges it. To call other GitBook API operations, such as writing the change request's content or getting the preview link, it uses a generic action that starts switched off until the admin turns it on. It is GitBook's official server and usage runs on your GitBook plan.

What it automates

What a Meteor Met does with GitBook

Find where an answer belongs in your help center

When your team notices a question keeps coming up on WhatsApp, the Met lists the GitBook sites, opens the help center's structure and tells you which section a new article fits in or which page already covers that topic.

Propose a change without touching what is published

The Met opens a change request in the right space, so the change stays as a reviewable draft in GitBook. What is published does not change until someone merges that change request.

Write the draft and get the preview

If the admin turns the generic action on, the Met calls the GitBook API operations that write the content into the change request and fetch the site data to build the change's preview link, which GitBook does not return in a single call.

Send the change for review

Once the draft is ready, the Met submits the change request for review so the person in charge approves it in GitBook. The same action can merge it, and merging publishes the change to the space.

5 tools

Everything your Met can ask GitBook for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_sites`	Lists the documentation sites in the connected GitBook organization.
`get_site_structure`	Returns the current structure of one of the organization's documentation sites.
`create_change_request`	Opens a change request in a space to draft changes without editing what is published.
`submit_or_merge_change_request`	Submits a change request for review or merges it, which publishes its changes to the space.
`invoke_operation`	Calls a GitBook API operation by name, such as getSpaceById. It starts switched off.

The limits

What the GitBook integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask for confirmation in the chat before writing to GitBook. The admin chooses in Connections which actions stay on; the generic API action starts switched off.
It does not set up Git Sync. According to GitBook, connecting GitHub or GitLab and choosing the repository and branch is a step done only in the app, whatever the connection method.
It is not the published docs MCP server. That other GitBook server is read-only for your readers; this one works on your organization with the account the admin authorizes.
It does not return a change request's preview link in a single call. It has to be built from the site data, and for that the Met needs the generic action switched on.
It sees no more than the account that authorized the connection. Sites, spaces or organizations that account cannot access stay out of reach.

Before you start

What you need to connect GitBook

1

A GitBook account with access to the documentation the Met will use

Connect with an account in your GitBook organization that can see the help center's sites and spaces, because the connector works with that account's permissions.
2

Connect it in Met

In Met, open Connections → GitBook → Connect. A GitBook window opens so you can sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about GitBook and Meteor

It proposes changes in a change request, which does not touch what is published. Merging it does publish the change: if you do not want the Met to do that, the admin turns that action off in Connections and your team merges in GitBook.

It calls GitBook API operations by name: writing a change request's content, reading a space or fetching a site's data. Since it opens the door to the GitBook API, it starts switched off.

Yes for reading the structure and proposing small changes in a change request. GitBook recommends that large changes to a synced space go through the repository, and Git Sync is not set up from the connector.

You do, with your own GitBook plan. Meteor does not resell GitBook: the connector uses your company's account and follows what your plan allows.

Step by step