For Cloudflare Nimbus docs

Ask AI for your Nimbus docs

Q: Does it work with Nimbus navigation?

Yes. Nimbus uses Astro’s ClientRouter, and astro-biel keeps the widget available across client-side navigation.

Q: Does Biel replace Nimbus’s agent-readable output?

No. Keep Nimbus’s Markdown alternates, llms.txt, sitemap, and structured data. Biel adds interactive chat, usage analytics, and an optional hosted MCP endpoint.

Keep Nimbus’s built-in search and agent-readable docs. Add source-linked chat with astro-biel, then expose the same documentation through hosted MCP when you need it.

Add Biel to Nimbus See the install code

14-day freeSelf-serveLive in 15 min

Biel.ai chatbot

Assistant

Hi! how can I help you?

Built for Nimbus’s Astro foundation

Add the chatbot through astro-biel, choose whether Nimbus or Biel should own page search, and connect a hosted MCP endpoint without changing how you author docs.

Full installation guide

Add astro-biel beside Nimbus

Nimbus produces an Astro site, so its existing integrations array can load Biel directly. Keep the Nimbus integration as configured and append biel(...).

→No Nimbus layout fork required for chat
→Works across Astro ClientRouter navigation
→Keeps Nimbus components and theme tokens untouched
→Source-linked answers from your indexed docs

astro.config.ts

// npm install astro-biel

import { defineConfig } from "astro/config"
import nimbus from "@cloudflare/nimbus-docs"
import biel from "astro-biel"

export default defineConfig({
  integrations: [
    nimbus(nimbusConfig, {
      // Keep the Nimbus options already in your project.
    }),
    biel({
      project: "<YOUR_PROJECT_ID>",
      headerTitle: "Documentation AI",
      buttonPosition: "bottom-right",
    }),
  ],
})

Choose how search should work

Nimbus already includes Pagefind search. Keep it and use Biel as a separate Ask AI surface, or set search: false in the Nimbus configuration and replace its SearchTrigger with Biel page search when you want page results and an Ask AI handoff in one interface.

→Keep Nimbus Pagefind when keyword search is enough
→Optional page results with an Ask AI handoff
→Disable Pagefind before replacing its Header.astro trigger
→Shares the chatbot project and indexed content

src/components/Header.astro

<div class="flex items-center gap-2">
  <biel-search-button
    project="<YOUR_PROJECT_ID>"
    header-title="Documentation AI"
    button-style="rounded">
      Search docs
  </biel-search-button>

  <ThemeToggle />
</div>

Make the same docs available to AI tools

Nimbus publishes agent-readable Markdown and llms.txt files. Biel adds a hosted MCP endpoint that lets compatible assistants query the indexed documentation interactively.

→Complements Nimbus’s llms.txt and Markdown routes
→Same index as the chatbot and Biel page search
→Works with Claude, Cursor, Cline, and other MCP clients
→Hosted endpoint, with no MCP server to operate

mcp.json

{
  "mcpServers": {
    "biel-ai": {
      "type": "http",
      "url": "https://mcp.biel.ai/v2/YOUR_PROJECT_SLUG/mcp"
    }
  }
}

What Biel adds to Nimbus

Nimbus already gives documentation teams strong search and agent-readable output. Biel adds an interactive answer layer and the feedback loop around it.

Dimension	Nimbus	Biel.ai
Reader experience	Nimbus includes fast, local full-text search powered by Pagefind.	Adds a separate Ask AI chatbot, with an optional page-search widget that can hand a question to chat.
Answers	Returns pages and matching passages for the reader to inspect.	Produces a source-linked answer when the reader does not know which page contains it.
Agent access	Publishes Markdown alternates, llms.txt, structured data, and other agent-readable surfaces.	Adds a hosted MCP endpoint for interactive retrieval from compatible assistants and development tools.
Content feedback	Provides authoring lint rules and content-structure guardrails.	Reports unanswered questions, ratings, and recurring topics so teams can prioritize documentation work.
Implementation	Search and agent-readable output ship with Nimbus.	Install astro-biel and append it to the existing Astro integrations array.

Things teams ask during evaluation

Does Nimbus need a dedicated Biel plugin?

No. Nimbus generates a standard Astro project, and its visible source is yours to edit. The astro-biel integration plugs into the existing astro.config.ts alongside nimbus(...).

Can we keep Nimbus search?

Yes. The recommended starting point is to keep Nimbus Pagefind search and add the Biel chatbot as a separate Ask AI surface. To replace Pagefind with Biel page search, set search: false in the Nimbus configuration before removing SearchTrigger; otherwise Nimbus’s keyboard shortcut remains active.

Does it work with Nimbus navigation?

Yes. Nimbus uses Astro’s ClientRouter, and astro-biel keeps the widget available across client-side navigation.

Does Biel replace Nimbus’s agent-readable output?

No. Keep Nimbus’s Markdown alternates, llms.txt, sitemap, and structured data. Biel adds interactive chat, usage analytics, and an optional hosted MCP endpoint.

Does it work when Nimbus is deployed to Cloudflare?

Yes. The widget runs in the browser and works with Nimbus’s static output and Cloudflare deployment path. Add the public documentation URL to Biel so it can be indexed.

What if Nimbus changes before 1.0?

The integration uses Astro’s standard integration API rather than a private Nimbus hook. If Nimbus changes the generated header, the optional search placement may move, but the chatbot configuration remains in astro.config.ts.

Make your Nimbus docs answer questions

Build your assistant Book a demo

14-day free trial · No credit card required

Use a different platform? See our integration pages for Astro, Starlight, Docusaurus, MkDocs, and Sphinx.