MCP server

This site hosts a Model Context Protocol server at /mcp, so an AI agent building tours with Bit.Bonboarding reads the library itself - its compiled API documentation, its guide, its stylesheet and these demo pages - instead of guessing at an API it half remembers. Every tool is read-only.

Connect a client

The endpoint is plain Streamable HTTP, so any MCP client connects with a URL and nothing else. The same tools are also served, version by version, through the bit platform's own server at https://bitplatform.dev/mcp, next to the other bit libraries.

// .mcp.json (Claude Code, VS Code, and anything else reading this shape)
{
  "mcpServers": {
    "bonboarding": {
      "type": "http",
      "url": "https://bonboarding.bitplatform.dev/mcp"
    }
  }
}

Tools

Tool	What it answers
`SearchBonboarding`	Everything at once - the guide, every public member, the theme variables and the demo sources - each hit with the exact follow-up call.
`GetBonboardingSetupGuide`	The complete wiring for one render mode: server, wasm, auto or standalone-wasm.
`GetBonboardingGuideSection`	One section of the reference guide, or the index of sections.
`GetBonboardingApi`	One public type with every parameter, property and method, its real default and its documentation - or the index of types.
`GetBonboardingThemeVariables`	Every `--bit-bonboarding-*` variable with its light and dark value.
`InspectBonboardingPlacement`	Where the library's own placement engine puts a popover for a given target, popover and viewport, and why.
`GetBonboardingSourceFile`	One demo file verbatim - every page here is a working tour - or the index of files.

The guide, the API, the theme and the sources are also exposed as bonboarding:// resources, and three prompts - add-bonboarding-to-app, implement-bonboarding-tour and debug-bonboarding-tour - walk an agent through the common jobs in the right order.

The same tools over plain HTTP

Every tool is also a GET under /api/mcp/...: open one in a browser tab to read exactly what an agent is handed.