Answer from the docs
A customer asks whether exports include archived records. The support lead asks Memtro, which searches the public docs space, finds the Exports page and quotes the passage with a link to send on.
GitBook + Memtro
Search every GitBook space you can open, read any page as markdown, and propose changes.
Connect GitBook with a personal access token and Memtro reads whatever that user can open: its organisations and spaces, a space's page tree, any page as markdown, and a full-text search across spaces. There is no sync. When you ask, and once an administrator has granted each action by name, it can open a change request, add, edit or delete pages inside it, request and give reviews, comment, and duplicate a space. Nothing is live until a change request is merged, and merging puts its edits in front of every reader of the space and its published site.
In Memtro
What you can do with GitBook in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right GitBook tool, reads what it needs, and answers with the source cited.
What it does
- 01The organisations the token's user belongs to, with plan, and the spaces in each
- 02Spaces by title with visibility, last update, open change requests and the published link
- 03A space's page tree in sidebar order, and any page as markdown, by id or by its path within the space
- 04Full-text search in one space or across an organisation, each hit with its breadcrumb and matching passages
- 05When asked and granted, opens a change request, adds, edits or deletes pages in it, retitles or archives it, and merges it into the live space that every reader sees
- 06When asked and granted, approves or requests changes, asks named members to review (GitBook notifies them), comments on change requests, spaces and pages or replies, and duplicates a space
Acts when asked
When you ask it to
These tools change something in GitBook. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Open a change request in a space
- 02Add, edit or delete pages inside a change request
- 03Retitle a change request, or set it to draft, open or archived
- 04Merge a change request into the live space
- 05Approve or request changes on a change request
- 06Ask named members to review a change request
- 07Comment on a change request
- 08Comment on a space or one of its pages
- 09Reply to a comment
- 10Duplicate a space
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in GitBook, choosing the same kinds; the tab shows GitBook's own steps. Each event can start a job, with the event as its input. GitBook signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01Content in a space was updated
- 02A visitor left feedback on a published page
- 03A visitor viewed a published page (high volume)
In practice
Ask it like you would a colleague
Once GitBook is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
GitBook + Memtro
Where in our docs do we explain webhook retries?
Read the 'Getting started → Install' page from the Developer docs space
Which spaces in the organisation have open change requests?
What does the API reference say about rate limits?
Open a change request fixing the rate limit on the API reference page to 600 a minute
A fix, proposed for review
Ben Okafor notices the API reference still gives the old rate limit and asks Memtro to correct it and ask Lucy Grant to review. Memtro opens a change request in GitBook, updates the page inside it and requests Lucy's review, and GitBook notifies her. Nothing reaches readers until the change request is merged.
Teams
Where it fits
The teams that lean on GitBook most, a question each of them asks, and what they connect beside it.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- People and onboardingThe answers a new hire would otherwise ask around forNew starter, Manager, People lead, Hiring manager“How do I request a laptop, and who approves it?”Used alongside Confluence, Notion, Google Drive, Slack, Google Calendar and 5 more.
Better together
Works with
A record in GitBook is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementGitBook with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementGitBook with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementGitBook with LinearIssues, projects and teams, synced hourly into memory.
- Email, calendar and chatGitBook with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatGitBook with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatGitBook with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
- Engineering and operationsGitBook with GitHubIssues, pull requests, code and commits, searchable by anyone who can ask a question.
- Engineering and operationsGitBook with AWS CloudWatchLogs, metrics and alarms from AWS, answered in plain English with the query that found them.
- Engineering and operationsGitBook with SentryAsk what is breaking in production and get the stack trace, not a dashboard.
Also in Documents and wikis
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Setup
How to connect
Connect withPersonal access token
- 1
In GitBook open the account menu → Settings → Developer → Personal access tokens and create a token. It acts as its user with no scopes, reading and editing whatever that user can, and is shown once
- 2
A dedicated member with access to just the right spaces is the safer token for Memtro
- 3
In Memtro open Connections → GitBook, paste the Personal access token and connect. In several organisations? Add the Organization id of the one to list and search by default
- 4
Ask where the docs explain something
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The GitBook tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in GitBook?+
Only when you ask, and only what it has been granted: open a change request in a space; add, edit or delete pages inside a change request; retitle a change request, or set it to draft, open or archived; merge a change request into the live space; approve or request changes on a change request; ask named members to review a change request; comment on a change request; comment on a space or one of its pages; reply to a comment; duplicate a space. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a GitBook connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my GitBook data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect GitBook?+
Personal access token. In GitBook open the account menu → Settings → Developer → Personal access tokens and create a token. It acts as its user with no scopes, reading and editing whatever that user can, and is shown once.
Can GitBook start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in GitBook, choosing the same kinds; the tab shows GitBook's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect GitBook in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.