GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing gitbook.com — GitBook CLI | GitBook Documentation

For the complete documentation index, see llms.txt. This page is also available as Markdown.

The GitBook CLI (@gitbook/cli) is a command-line tool for working with your GitBook content and organizations directly from your terminal.

It wraps the GitBook API as a set of commands, so you can list organizations, inspect spaces and pages, ask questions against your docs, and build and publish integrations — all without leaving the shell.

Human and agentic workflows

The CLI is built for two kinds of use:

Human-driven — you type commands in your terminal to look things up, script one-off tasks, or manage integrations by hand. Output is formatted for readability in an interactive shell.
Agentic coding — an AI coding agent (Claude Code, Codex, Cursor, and similar) runs the CLI on your behalf as part of a larger task. Machine-readable output (--json) and predictable command structure make it easy for an agent to call commands, parse results, and chain them together.

If you want an AI agent to create and edit content through GitBook’s API using a purpose-built protocol, see GitBook MCP. The CLI is a good fit when you want scriptable commands, integration development, or an agent that already works comfortably in a terminal.

Install

The GitBook CLI requires Node v18 or later. Install it globally from npm:

npm install @gitbook/cli -g

This installs the gitbook command. Check it's working:

gitbook --version

Authenticate

The quickest way to sign in is through your browser:

gitbook login

This opens GitBook in your browser, asks you to authorize the CLI, and stores the resulting token locally. Sessions are refreshed automatically.

This is the recommended path for everyday use.

To skip the browser flow — for CI, scripts, or publishing integrations — authenticate with a personal API token. Create one at app.gitbook.com/account/developer, then run:

gitbook auth --token <token>

If you omit --token, the CLI prompts you for it.

Confirm who you're signed in as at any time:

To sign out, run gitbook logout.

Publishing integrations (gitbook integration publish / unpublish) requires a personal API token — the browser (OAuth) session can't perform those operations. Run gitbook auth --token <token> for publishing workflows. The two credentials can coexist, so you can use browser sign-in for everyday commands and a token for publishing.

Run your first commands

Most commands are generated from the GitBook API and grouped by resource — organizations, spaces, collections, and so on. Start by listing the organizations you belong to:

Grab an organization ID from that output, then list its spaces:

Fetch the details of a single space:

List the pages in a space:

Path parameters like <spaceId> can be passed as a positional argument or as a flag — gitbook spaces get <spaceId> and gitbook spaces get --spaceId <spaceId> are equivalent.

Run gitbook --help to browse the full command tree, or add --help to any command (for example gitbook spaces --help) to see its subcommands and options.

Output formats

Every API command supports the same output flags:

Flag

Output

--pretty

Human-readable summaries (default in an interactive terminal)

--json

JSON — best for scripts and agents

--yaml

YAML

--full

Show every field instead of the compact summary

If you don't pass a flag, the CLI picks a sensible default: pretty output in an interactive terminal, and YAML when the output is piped or redirected. Pass --json explicitly when you're piping into tools like jq:

Ask your docs a question

The CLI can query your content with natural language and stream the answer back as it's generated:

The answer streams to your terminal, followed by its sources and suggested follow-up questions. Press Ctrl-C to stop early and keep whatever streamed so far.

Drive the CLI from an AI coding agent

Because the CLI is scriptable and speaks JSON, an AI coding agent can use it as a tool while it works. Point your agent at the commands above and let it authenticate, explore your content, and act on the results.

Explore an organization’s docs from the terminal.

Answer a question using my docs and cite sources.

Build integrations

Beyond querying content, the CLI is the primary tool for developing GitBook integrations. Scaffold a new project with:

Then use gitbook integration dev to run it locally and gitbook integration publish to ship it. See the integrations documentation for the full development workflow.

Last updated 3 months ago

Was this helpful?

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.