GitBook MCP connector
The GitBook connector brings your GitBook organizations, members, teams, invites, and documentation sites into Elaichi, so Claude, ChatGPT, Cursor, or the Elaichi Agent can look them up and manage them as the person who signed in.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
59 tools
How to connect
How to connect GitBook to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect GitBook once
-
Open Connections, choose Add connection, and pick GitBook.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a GitBook API key. One person generates a token in GitBook and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
GitBook MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
GitBook MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
GitBook MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect GitBook to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with GitBook through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Documentation
Spin up a new docs site
Ask for a new GitBook site when a product or internal handbook needs its own home, and it is created in the right organization without opening a browser tab.
-
IT
Invite new hires and remove leavers
Send a GitBook invite to everyone starting on Monday, and remove members who have left, from one conversation instead of one admin screen at a time.
-
Engineering
Organize contributors into teams
Create a GitBook team for a new squad, rename one after a reorg, and check who is on each team before handing them a space to maintain.
-
Support
See who can edit the help center
Ask which GitBook members and teams have access to the organization behind your public help center before a big release lands.
-
Operations
Clean up stale invitations
List every pending GitBook invite, spot the ones sent months ago to people who never joined, and withdraw them in a single pass.
-
People
Change a member's role after a move
When someone moves from contributor to admin, or the other way, update their GitBook organization membership and confirm the change without asking IT to do it.
Try asking
- “List GitBook organization members added this month”
- “Which GitBook invites are still pending”
- “Show GitBook users in the Docs organization”
Compare
Elaichi vs Zapier MCP vs Composio for GitBook
All three can connect GitBook to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over GitBook tools | Allow or restrict single GitBook tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per GitBook call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
GitBook tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect GitBook, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting GitBook gets you
6 screens from the product, each doing one job for your GitBook account.
The agent
Ask about GitBook members in plain language.
The agent answers from live GitBook organizations, members and invites.
- organizations
- members
- invites
- users
Ask Elaichi to work across your apps.
List GitBook organization members added this month
Which GitBook invites are still pending
Show GitBook users in the Docs organization
Also runs in Claude, ChatGPT or Cursor
MCP clients
Reach GitBook from Claude, ChatGPT or Cursor.
One governed MCP endpoint, no SDK and no shared GitBook API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
59 GitBook tools are ready to call.
Organizations, members, invites and users are covered without custom code.
- List all GitBook user
- Get single GitBook user by ID
- Update a GitBook user by ID
- List all GitBook organizations
ElaichiToolsToolboxes
Every team gets its own GitBook toolbox.
Curate GitBook tools per toolbox and scope each one to a team.
- Docs
- Engineering
- Support
- Product
ElaichiToolboxesShared connections
Teammates use GitBook without touching a credential.
See who connected each GitBook account and which teams and members share it.
- Docs Core
- Engineering
- Support
- Product Marketing
ElaichiConnectionsAudit log
Every GitBook call is written down.
When, who, what happened, type and resource for each GitBook request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your GitBook digest.
Six steps fetch and group GitBook members, draft, wait for approval, post back.
GitBook digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch organizations
GitBook
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
GitBook
Queued
Collections and dashboards
GitBook health numbers land on a schedule.
Four metrics, 14 days of records created, and a breakdown by team.
GitBook health
Refreshed 4 minutes ago · every 15 minutes · from the organizations collection
Organizations
1,284 ↓ 12%
Members
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Organizations created
Last 14 days
By team
Share of activity
Docs Core 34%
Engineering 27%
Support 21%
Product Marketing 18%
FAQ
Frequently asked questions
How do I connect GitBook to Claude?
First connect GitBook in Elaichi by pasting an API key from your GitBook account settings. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.
Does GitBook work with ChatGPT and Cursor as well as Claude?
Yes. Once GitBook is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect GitBook once and every client you use picks it up.
What can an AI agent actually do with my GitBook data?
With GitBook connected, an agent can list your organizations, members, teams, and documentation sites, look up a specific person or team, send or withdraw invites, update a member's role, create or rename teams, and create a new site. Because GitBook offers a large set of actions, short concrete asks such as "list pending GitBook invites" work better than long paragraphs.
Does connecting GitBook give the AI access to my whole organization?
No. Every request runs as the person who signed in, so the agent sees only the GitBook organizations, members, and sites that person can already see, and GitBook's own permissions still apply. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what GitBook itself allows.
Can I stop an agent from deleting or changing things in GitBook?
Yes. Restrictions in Elaichi apply per action, so you can allow listing GitBook members and sites while blocking anything that deletes an organization, removes a member, or changes a team. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.
What happens to a GitBook connection when someone leaves?
When you offboard a person in Elaichi, their access to GitBook through every AI client ends at once. A GitBook connection they were sharing keeps working for the rest of the team. If you later disconnect GitBook once in Elaichi, it is removed from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the GitBook MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. GitBook is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for GitBook?
Yes. Both let Claude, ChatGPT or Cursor use GitBook. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every GitBook call.
How is Elaichi different from Composio for GitBook?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to GitBook: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put GitBook in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.