New this month: Generate MCP servers from your docs, plus merge rules and more

It’s been a busy month here at GitBook, packed with releases that make your docs better than ever. From changes that your customers will love to improvements you’ll notice when editing your content, there’s a lot to talk about.

Lets dive in!

Generate an MCP server from your docs

GitBook now automatically generates an MCP server for your documentation.

With MCP servers in GitBook, your users can access knowledge from your docs in AI tools and other platforms they choose to connect to. Users can quickly copy a link to your MCP server from the Page actions menu — you can enable or disable this option in your site’s customization options — and connect it to whichever tools they want.

For example, a user could add your docs MCP server to VS Code to pull answers or even insert information from your docs directly into their editor via MCP calls.

This joins our suite of AI-ready documentation optimizations such as llms.txt, llms-full.txt, Markdown exports, and quick actions to open pages in ChatGPT or Claude.

Merge rules

This month we’ve got a bunch of improvements focused on improving change requests. Starting with merge rules — which bring another layer of quality control to your docs.

Merge rules let you define requirements that must be met before anyone can merge a change request. You can set rules within each individual space, or set rules that apply across your entire organization — then set up overrides in specific spaces if needed.

A screenshot of GitBook showing the Merge rules screen with two rules configured

We’ve included a bunch presets to make it easy for you to get set up — like a change request requiring a title, description, or approval from specific reviewers. And you can combine rules for complex workflows, or write dynamic expressions using the same language as adaptive content.

If the merge rules aren’t met, the Merge button is disabled with a tooltip and information in the overview explaining why.

We’re rolling merge rules out in early access right now. It'll be available to everyone on the Pro plan soon.

Change request improvements

Alongside merge rules, change requests now also include a more detailed and useful Overview sidebar. Here you can add a description, manage the reviewers, check the status of reviews, and copy a link — all with a GitHub-inspired UI that will feel instantly familiar.

A screenshot of GitBook showing the new change request overview panel that includes a description, merge rules, participants and reviewers

We’ve also improved reviews. Now, previous reviews are marked outdated when you re-request or add a new review, and there’s a button to re-request a review.

This improved side panel and review flow pairs nicely with merge rules and sets the stage for Docs Agents — we should have more news to share about that soon.

When you’re viewing your docs site, it’s often useful to be able to jump straight to your site’s settings, insights or editing options. That’s why we’ve added a new toolbar when you’re viewing your live docs site, or when viewing a change request preview in its own tab.

A screenshot of a change request deploy preview for a GitBook docs site. The screenshot is zoomed in to the lower part of the screen and shows a hovering toolbar with options that let viewers jump quickly back to the GitBook app to access useful functions

When you’re previewing a change request, the toolbar lets you quickly jump to the GitBook app to edit or leave feedback — or visit the live site. This toolbar is only visible to people viewing the change request preview.

A similar toolbar also appears on you live docs site — although this one is only visible to members of your organization. So if you or one of your teammates visits your live site, the toolbar will help you jump straight to the GitBook app to change settings, customization, or content, or check site insights.

One important thing to note: This new site toolbar is not visible to anyone outside of your GitBook organization. That means it will not appear for your end-users when they visit your docs site.

Nested section groups

Now let’s move on to some features that will benefit your end-users.

First, you can now add multiple section groups within a section group and give them all a title and icon. And you can even mix sections and nested groups — with sections displaying in a separate area within the group menu.

A screenshot of a published docs site in GitBook. The image is cropped to the top-left corner and focused on the navigation bar. A section group is open and inside you can see more site sections and another section group, forming a split navigation window that's nicely designed.

This unlocks awesome new options for building an extensive, hierarchical navigation for your docs site.

While we’re talking about sections, we’ve also improved the section bar with faded edges and scroll buttons when content exceeds the container, plus responsiveness fixes for better positioning.

Search scope controls

Site search now lets users choose the scope of their search by site sections, not only by variants.

By default, search shows the best match — from the current variant and the default variant of other sections. Users can now narrow their search to the current section or broaden to all variants across all sections.

a screnshot of a search panel in a published GitBook site. At the top of the search results is a new toggle that lets you switch the scope of your search

We’ve also removed language variants from scope options to avoid clutter and confusion.

And of course, we automatically show the right buttons based on your site setup — so if you head to our own docs, for example, you’ll see only three options when you search, as we don’t use variants.

Editor improvements

Alongside these user-facing improvements, our editor team has also been focused on some smaller improvements that make maintaining your docs better than ever. Here are a few highlights:

Fit and fill options for card images

Before, images in cards would be cropped automatically depending on your readers’ screen size. But that made it hard to choose a good card image, and meant portrait images would always be cropped.

With this release, card images now support three display modes:

Crop to 16:9 or 1:1 (as before).Stretch to fill the box.Fit fully within the box, using your primary color to fill background space.

Page outline improvements

The page outline makes it easy to see and jump to all the sections of a page. And with this release we’ve made a few small improvements.

First, we’ve separated the On this page title from the outline, made it sticky, and added an icon to make it easier to see when browsing.

Plus, for long pages, the page outline’s scroll stays in sync with page scroll, keeping the active item in view. This should make navigating long content feel smoother.

Vertical alignment in columns

One final small update that makes column blocks more powerful — you can now vertically align content in a column block. That’s ideal for centered or bottom-aligned layouts on landing pages or alongside images. Head to our changelog to see what we mean.

That’s not all…

This is a quick summary of this month’s biggest releases — but there’s also a bunch of other stuff we released this month that we haven’t mentioned here. Check out the changelog to read about all that good stuff.

→ Read the changelog

→ Get started with GitBook for free

→ Last month’s updates: Auto-updating translations, AI Assistant, new insights and more

It’s been a busy month here at GitBook, packed with releases that make your docs better than ever. From changes that your customers will love to improvements you’ll notice when editing your content, there’s a lot to talk about.

Lets dive in!

Generate an MCP server from your docs

GitBook now automatically generates an MCP server for your documentation.

With MCP servers in GitBook, your users can access knowledge from your docs in AI tools and other platforms they choose to connect to. Users can quickly copy a link to your MCP server from the Page actions menu — you can enable or disable this option in your site’s customization options — and connect it to whichever tools they want.

For example, a user could add your docs MCP server to VS Code to pull answers or even insert information from your docs directly into their editor via MCP calls.

This joins our suite of AI-ready documentation optimizations such as llms.txt, llms-full.txt, Markdown exports, and quick actions to open pages in ChatGPT or Claude.

Merge rules

This month we’ve got a bunch of improvements focused on improving change requests. Starting with merge rules — which bring another layer of quality control to your docs.

Merge rules let you define requirements that must be met before anyone can merge a change request. You can set rules within each individual space, or set rules that apply across your entire organization — then set up overrides in specific spaces if needed.

We’ve included a bunch presets to make it easy for you to get set up — like a change request requiring a title, description, or approval from specific reviewers. And you can combine rules for complex workflows, or write dynamic expressions using the same language as adaptive content.

If the merge rules aren’t met, the Merge button is disabled with a tooltip and information in the overview explaining why.

We’re rolling merge rules out in early access right now. It'll be available to everyone on the Pro plan soon.

Change request improvements

Alongside merge rules, change requests now also include a more detailed and useful Overview sidebar. Here you can add a description, manage the reviewers, check the status of reviews, and copy a link — all with a GitHub-inspired UI that will feel instantly familiar.

We’ve also improved reviews. Now, previous reviews are marked outdated when you re-request or add a new review, and there’s a button to re-request a review.

This improved side panel and review flow pairs nicely with merge rules and sets the stage for Docs Agents — we should have more news to share about that soon.

When you’re viewing your docs site, it’s often useful to be able to jump straight to your site’s settings, insights or editing options. That’s why we’ve added a new toolbar when you’re viewing your live docs site, or when viewing a change request preview in its own tab.

When you’re previewing a change request, the toolbar lets you quickly jump to the GitBook app to edit or leave feedback — or visit the live site. This toolbar is only visible to people viewing the change request preview.

A similar toolbar also appears on you live docs site — although this one is only visible to members of your organization. So if you or one of your teammates visits your live site, the toolbar will help you jump straight to the GitBook app to change settings, customization, or content, or check site insights.

One important thing to note: This new site toolbar is not visible to anyone outside of your GitBook organization. That means it will not appear for your end-users when they visit your docs site.

Nested section groups

Now let’s move on to some features that will benefit your end-users.

First, you can now add multiple section groups within a section group and give them all a title and icon. And you can even mix sections and nested groups — with sections displaying in a separate area within the group menu.

This unlocks awesome new options for building an extensive, hierarchical navigation for your docs site.

While we’re talking about sections, we’ve also improved the section bar with faded edges and scroll buttons when content exceeds the container, plus responsiveness fixes for better positioning.

Search scope controls

Site search now lets users choose the scope of their search by site sections, not only by variants.

By default, search shows the best match — from the current variant and the default variant of other sections. Users can now narrow their search to the current section or broaden to all variants across all sections.

We’ve also removed language variants from scope options to avoid clutter and confusion.

And of course, we automatically show the right buttons based on your site setup — so if you head to our own docs, for example, you’ll see only three options when you search, as we don’t use variants.

Editor improvements

Alongside these user-facing improvements, our editor team has also been focused on some smaller improvements that make maintaining your docs better than ever. Here are a few highlights:

Fit and fill options for card images

Before, images in cards would be cropped automatically depending on your readers’ screen size. But that made it hard to choose a good card image, and meant portrait images would always be cropped.

With this release, card images now support three display modes:

Crop to 16:9 or 1:1 (as before).Stretch to fill the box.Fit fully within the box, using your primary color to fill background space.

Page outline improvements

The page outline makes it easy to see and jump to all the sections of a page. And with this release we’ve made a few small improvements.

First, we’ve separated the On this page title from the outline, made it sticky, and added an icon to make it easier to see when browsing.

Plus, for long pages, the page outline’s scroll stays in sync with page scroll, keeping the active item in view. This should make navigating long content feel smoother.

Vertical alignment in columns

One final small update that makes column blocks more powerful — you can now vertically align content in a column block. That’s ideal for centered or bottom-aligned layouts on landing pages or alongside images. Head to our changelog to see what we mean.

That’s not all…

This is a quick summary of this month’s biggest releases — but there’s also a bunch of other stuff we released this month that we haven’t mentioned here. Check out the changelog to read about all that good stuff.

→ Read the changelog

→ Get started with GitBook for free

→ Last month’s updates: Auto-updating translations, AI Assistant, new insights and more

It’s been a busy month here at GitBook, packed with releases that make your docs better than ever. From changes that your customers will love to improvements you’ll notice when editing your content, there’s a lot to talk about.

Lets dive in!

Generate an MCP server from your docs

GitBook now automatically generates an MCP server for your documentation.

With MCP servers in GitBook, your users can access knowledge from your docs in AI tools and other platforms they choose to connect to. Users can quickly copy a link to your MCP server from the Page actions menu — you can enable or disable this option in your site’s customization options — and connect it to whichever tools they want.

For example, a user could add your docs MCP server to VS Code to pull answers or even insert information from your docs directly into their editor via MCP calls.

This joins our suite of AI-ready documentation optimizations such as llms.txt, llms-full.txt, Markdown exports, and quick actions to open pages in ChatGPT or Claude.

Merge rules

This month we’ve got a bunch of improvements focused on improving change requests. Starting with merge rules — which bring another layer of quality control to your docs.

Merge rules let you define requirements that must be met before anyone can merge a change request. You can set rules within each individual space, or set rules that apply across your entire organization — then set up overrides in specific spaces if needed.

We’ve included a bunch presets to make it easy for you to get set up — like a change request requiring a title, description, or approval from specific reviewers. And you can combine rules for complex workflows, or write dynamic expressions using the same language as adaptive content.

If the merge rules aren’t met, the Merge button is disabled with a tooltip and information in the overview explaining why.

We’re rolling merge rules out in early access right now. It'll be available to everyone on the Pro plan soon.

Change request improvements

Alongside merge rules, change requests now also include a more detailed and useful Overview sidebar. Here you can add a description, manage the reviewers, check the status of reviews, and copy a link — all with a GitHub-inspired UI that will feel instantly familiar.

We’ve also improved reviews. Now, previous reviews are marked outdated when you re-request or add a new review, and there’s a button to re-request a review.

This improved side panel and review flow pairs nicely with merge rules and sets the stage for Docs Agents — we should have more news to share about that soon.

When you’re viewing your docs site, it’s often useful to be able to jump straight to your site’s settings, insights or editing options. That’s why we’ve added a new toolbar when you’re viewing your live docs site, or when viewing a change request preview in its own tab.

When you’re previewing a change request, the toolbar lets you quickly jump to the GitBook app to edit or leave feedback — or visit the live site. This toolbar is only visible to people viewing the change request preview.

A similar toolbar also appears on you live docs site — although this one is only visible to members of your organization. So if you or one of your teammates visits your live site, the toolbar will help you jump straight to the GitBook app to change settings, customization, or content, or check site insights.

One important thing to note: This new site toolbar is not visible to anyone outside of your GitBook organization. That means it will not appear for your end-users when they visit your docs site.

Nested section groups

Now let’s move on to some features that will benefit your end-users.

First, you can now add multiple section groups within a section group and give them all a title and icon. And you can even mix sections and nested groups — with sections displaying in a separate area within the group menu.

This unlocks awesome new options for building an extensive, hierarchical navigation for your docs site.

While we’re talking about sections, we’ve also improved the section bar with faded edges and scroll buttons when content exceeds the container, plus responsiveness fixes for better positioning.

Search scope controls

Site search now lets users choose the scope of their search by site sections, not only by variants.

By default, search shows the best match — from the current variant and the default variant of other sections. Users can now narrow their search to the current section or broaden to all variants across all sections.

We’ve also removed language variants from scope options to avoid clutter and confusion.

And of course, we automatically show the right buttons based on your site setup — so if you head to our own docs, for example, you’ll see only three options when you search, as we don’t use variants.

Editor improvements

Alongside these user-facing improvements, our editor team has also been focused on some smaller improvements that make maintaining your docs better than ever. Here are a few highlights:

Fit and fill options for card images

Before, images in cards would be cropped automatically depending on your readers’ screen size. But that made it hard to choose a good card image, and meant portrait images would always be cropped.

With this release, card images now support three display modes:

Crop to 16:9 or 1:1 (as before).Stretch to fill the box.Fit fully within the box, using your primary color to fill background space.

Page outline improvements

The page outline makes it easy to see and jump to all the sections of a page. And with this release we’ve made a few small improvements.

First, we’ve separated the On this page title from the outline, made it sticky, and added an icon to make it easier to see when browsing.

Plus, for long pages, the page outline’s scroll stays in sync with page scroll, keeping the active item in view. This should make navigating long content feel smoother.

Vertical alignment in columns

One final small update that makes column blocks more powerful — you can now vertically align content in a column block. That’s ideal for centered or bottom-aligned layouts on landing pages or alongside images. Head to our changelog to see what we mean.

That’s not all…

This is a quick summary of this month’s biggest releases — but there’s also a bunch of other stuff we released this month that we haven’t mentioned here. Check out the changelog to read about all that good stuff.

→ Read the changelog

→ Get started with GitBook for free

→ Last month’s updates: Auto-updating translations, AI Assistant, new insights and more