MCP server
This site hosts a Model Context Protocol server at /mcp, so an AI agent adding a command palette with
Bit.Balette reads the library itself - its compiled API documentation, its guide, its stylesheet's variables, its
real matcher 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.
// .mcp.json (Claude Code, VS Code, and anything else reading this shape)
{
"mcpServers": {
"balette": {
"type": "http",
"url": "https://balette.bitplatform.dev/mcp"
}
}
}Tools
| Tool | What it answers |
|---|---|
SearchBalette |
Everything at once - the guide, every public member, the theme variables, the setup guides and the demo sources - each hit with the exact follow-up call. |
GetBaletteSetupGuide |
The complete wiring for one render mode: server, wasm, auto, standalone-wasm or hybrid. |
GetBaletteGuideSection |
One section of the reference guide, or the index of sections. |
GetBaletteApi |
One public type with every parameter, property and method, its real default and its documentation - or the index of types. |
GetBaletteThemeVariables |
Every --bit-balette-* custom property with its light and dark value, and the data-balette attributes to style an unstyled palette by. |
InspectBaletteSearch |
Runs the library's own matcher and ranker over a query and a list of commands, and reports each score, the highlighted positions and the final order. |
GetBaletteSourceFile |
One demo or library file verbatim - every page here is a working palette feature - or the index of files. |
Called without a key, the Get… tools answer with their index - the setup guides, the guide's sections, the
types, the files - to pick from.
Resources and prompts
The guide, the API, the theme variables and the sources are also exposed as resources:
| Resource | Holds |
|---|---|
balette://guide | The reference guide, whole |
balette://guide/{heading} | One section of it |
balette://api | The public API's index |
balette://api/{typeName} | One type, with its members |
balette://theme | The theme variables |
balette://source/{path} | One demo or library file |
And three prompts walk an agent through the common jobs in the right order:
| Prompt | Takes | Does |
|---|---|---|
add-balette-to-app | renderMode: server, wasm, auto, standalone-wasm, hybrid or unknown | Adds Bit.Balette to an existing app, in the right order for its render mode - working the mode out first when it is unknown. |
implement-balette-feature | feature, in your own words | Implements commands, nested pages, prompts, multi-select, modes, sources, shortcuts or theming with the real API. |
debug-balette-palette | symptom | Diagnoses Ctrl K doing nothing, an unstyled palette, a missing, oddly ranked or stale command, a silent shortcut or an empty source. |
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.