# GitBook (ChatGPT App)

> Create and edit GitBook docs

- Type: app
- Publisher: Gitbook Inc. (official)
- Categories: Development, Productivity
- Website: https://chatgpt.com/plugins/plugin_asdk_app_6a576f075ec4819196c203b7049542be
- Open in ChatGPT: https://chatgpt.com/plugins/plugin_asdk_app_6a576f075ec4819196c203b7049542be
- Version: 1.0.0
- Listed: 2026-10-04

## About

The GitBook MCP server gives AI agents a full read/write connection to your GitBook organization. Create and configure docs sites, spaces, and sections; draft, edit, and restructure content; open change requests and push updates for review; publish OpenAPI specs; and manage site customization — all through natural conversation, with OAuth sign-in or a personal access token. Pairs with the GitBook Skills plugin, which teaches agents how to use these capabilities effectively.

## How to use

1. **Add it in ChatGPT** Open GitBook in ChatGPT's Plugin directory (button above), select + to add it and sign in if asked.

2. **Use it in a chat** Type @ in the composer and pick GitBook, or start your message with its name. ChatGPT may also suggest it when it fits what you ask.

## Skills

- **configure-site**: Create and maintain entire GitBook documentation sites end-to-end — design the site structure from source content, scaffold a Git repository in monorepo layout, set up the GitHub/GitLab remote, drive the GitBook API (via its REST API or MCP server) to create the site/sections/spaces, apply branded customization, and hand the user clean instructions for the one UI step (Git Sync wiring) that GitBook does not expose programmatically. Trigger this skill whenever the user wants to spin up a new GitBook docs site, restructure or extend an existing one, link spaces to a Git repo for sync, change a site's branding (logo, colors, fonts, header/footer), or programmatically manage spaces, sections, or site-spaces. This skill is the orchestration layer; for authoring the markdown content of any individual page it defers to the companion `write-docs` skill.
- **cr-create**: Drive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new page), request reviewers, notify Slack, then pull review comments back in, fix them, re-push, and resolve. This is the authoring-side companion to cr-review (the reviewer side over the same API). Use this whenever someone wants to run a "docs review in GitBook" loop from the terminal/agent against the raw API (curl/HTTP), mentions creating a change request via the API, pushing content into a CR, "pull in the latest comments and fix them," requesting review on docs, or showing engineers how to collaborate on GitBook docs from Claude + Slack without a CLI.
- **write-docs**: Write, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor. Use whenever a task involves creating or editing a GitBook markdown page, writing or updating a README.md or SUMMARY.md, inserting a hint, tab, stepper, card, or other GitBook block, configuring page frontmatter or layout options, setting up variables or expressions, or formatting content for GitBook outside the GitBook UI.
- **write-openapi**: Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI block or `{% openapi %}` block, adding or updating an OpenAPI/Swagger spec in GitBook (by file or URL, via the API, MCP, CLI, or app UI), generating API reference pages from a spec, configuring the interactive "Test it" runner (auth, servers, CORS, proxy), customizing pages with GitBook `x-*` extensions (icons, titles, navigation hierarchy, code samples, enum descriptions), marking operations experimental/deprecated/hidden, or automating spec updates in CI/CD. Trigger even when the user only mentions GitBook plus OpenAPI, puts an `x-` extension on a spec destined for GitBook, or asks "why isn't my spec loading" or "why doesn't Test it work", without naming this skill.

## Example prompts

- "Turn my markdown folder into a GitBook docs site"
- "Update the docs for this page and open a change request for review"
- "Publish my OpenAPI spec as interactive API reference docs"

## Related

- [Google Drive](https://chatgptplugins.directory/apps/google-drive.md): Search and work with Drive, Docs, Sheets and Slides
- [GitHub](https://chatgptplugins.directory/apps/github.md): Triage PRs, issues and CI across your repositories
- [Figma](https://chatgptplugins.directory/apps/figma.md): Create designs, diagrams and FigJam boards and ship them to code
- [MCP App Basics (Apps SDK example)](https://chatgptplugins.directory/apps/apps-sdk-mcp-app-basics.md): Eleven interactive widgets that each teach one MCP Apps API
- [Cards Against AI (Apps SDK example)](https://chatgptplugins.directory/apps/apps-sdk-cards-against-ai.md): Card game driven by ChatGPT with a real-time synced widget
- [Authenticated Server (Apps SDK example)](https://chatgptplugins.directory/apps/apps-sdk-authenticated.md): Demonstrates tools that require different levels of OAuth

---
Source: https://chatgptplugins.directory/apps/gitbook · Index: https://chatgptplugins.directory/llms.txt · Independent and community-run. Not affiliated with or endorsed by OpenAI. ChatGPT is a trademark of OpenAI.