MCP server

This site hosts a Model Context Protocol server at /mcp, so an AI agent writing form code with Bit.Borm reads the library itself - its compiled API documentation, its guide, its stylesheet, its own JSON Schema importer 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": {
    "borm": {
      "type": "http",
      "url": "https://borm.bitplatform.dev/mcp"
    }
  }
}

Tools

Tool	What it answers
`SearchBorm`	Everything at once - the guide, every public member, the setup guides, the theme, the stylesheet and the demo's working forms - each hit with the exact follow-up call that returns its full text.
`GetBormSetupGuide`	The complete wiring for one hosting model: web-app, webassembly, server or hybrid - `AddBorm()` in every container that renders a form, and the stylesheet link.
`GetBormGuideSection`	One section of the reference guide, or the index of sections.
`GetBormApi`	One public type with every parameter, property and method, its real default and its documentation - or the index of types.
`GetBormTheme`	The `--bit-borm-*` custom properties with their light and dark values and what each one is for - or one of them in full, with the override to write in every colour mode.
`InspectBormSchema`	What the library makes of a JSON Schema document - the form it becomes, field by field, what `Validate()` reports, what the importer drops without a word, and the document it exports back - or a sample schema, to see the format.
`GetBormSourceFile`	One demo or library file verbatim - every page here is a working form - or the index of files.

The guide, the API, the theme, a sample schema and the sources are also exposed as borm:// resources, and three prompts - add-borm-to-app, implement-borm-form and debug-borm-form - 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.

Edit this page on GitHub