
Overview
When a feature ships, the docs page that explains it goes stale. Fixing it means finding the page, rewriting the section and getting it reviewed before it goes live.
Connect GitBook through its official MCP server and Agent M drafts your changes in a change request, then gives you the link to review and merge it in GitBook. On a space synced with Git, merging also commits the change to your repository.
Any member can connect their own GitBook account from its connector page in Maintouch.
Approve access in GitBook’s sign-in window. Nothing to copy or paste.
Your connection starts private to you. Turn on sharing to let your teammates’ chats use it too.
Ask for a docs change and Agent M edits the pages in a new change request, then gives you the link to review it.
Agent M merges or publishes only when you ask, so nothing goes live without you.
A custom agent can keep your docs current as part of its instructions and report the change request to review.
Agent M works through your GitBook account, so it only reaches the organizations, sites and spaces your account can.
Only when you ask. Changes go in a change request by default, and Agent M asks before merging, publishing, deleting anything or changing settings and members.
Yes. Agent M edits through change requests as usual, and merging one commits the change to your synced repository. GitBook needs push access to that branch for the sync to go through.
Anything your GitBook account cannot do. Merge rules and permissions set in GitBook still apply.
Only if you share it. A new connection is private to you, and you can open it to your org from the GitBook connector page.