GitBook Documentation

Documentation your users actually read

Write in the editor, drive it from your agent, or sync it from Git. Publish a docs site your team maintains without fighting it.

Quickstart GitBook MCP

How do you want to work?

The same docs, three ways in. Most teams use more than one.

In the editor

Write and publish visually. Blocks, change requests, and review without touching a terminal.

Quickstart

Format content

Publish a docs site

From your agent

Drive GitBook from Claude, Cursor, or any MCP client. Draft, restructure, and open change requests.

GitHub & GitLab Sync

GitBook MCP

Agent skills

With code

Sync from Git, script with the CLI, or build on the API and ship your own components.

GitBook CLI

API reference

Build a custom component

From first draft to published site

Follow it end to end, or pick up where you left off.

CREATE

Get content in

Start fresh or bring what you have.

COLLABORATE

Work as a team

Review before anything goes live.

PUBLISH

Ship your site

Structure, brand, and control access.

Embed in your product

IMPROVE

Learn what works

See what readers need next.

Automatic docs improvements

AI out of the box

Two work for you while you write. Two work for your readers after you publish.

WRITES WITH YOU

GitBook Agent

Drafts, edits, reviews change requests, and flags gaps against your style guide.

FINDS THINGS

AI Search

Natural-language search across your content, in the app and on your published site.

ANSWERS READERS

GitBook Assistant

Answers questions on your site from your docs and connected support sources.

SERVES AGENTS

MCP for your docs

Your published docs as a tool, so your customers' agents can read them properly.

Keep going

Concepts

Learn about GitBook concepts.

Changelog

See our latest releases.

Support

Last updated 3 days ago

Was this helpful?