Skip to content

MCP server

This site hosts a Model Context Protocol server at /mcp, so an AI agent adding collaboration with Bit.Bcrdt reads the library itself - the compiled API documentation of its four packages, its guide, its real CRDT engine and decoders, and these demo pages - instead of guessing at an API it half remembers, or at what a merge will decide. 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: https://bcrdt.bitplatform.dev/mcp, or http://localhost:5560/mcp while the demo runs locally. 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": {
    "bcrdt": {
      "type": "http",
      "url": "https://bcrdt.bitplatform.dev/mcp"
    }
  }
}

Tools

ToolWhat it answers
SearchBcrdt Everything at once - the guide, every public member of the four packages, the setup guides and the demo sources - each hit with the exact follow-up call.
GetBcrdtSetupGuide The complete wiring for one hosting model - web-app, standalone-wasm, server, hybrid, websocket or console - or the index of them.
GetBcrdtGuideSection One section of the reference guide, or the index of sections.
GetBcrdtApi One public type with its constructors, parameters, properties and methods, their real defaults and their documentation - or the index of types.
InspectBcrdtMerge Runs the real engine on concurrent edits by two to four replicas and reports each one's state before the merge, what they converge to, every update's size, and what was decided - one value wins for a map key, both survive in a text.
InspectBcrdtUpdate Decodes an update or a protocol message - its kind, the blocks per client, the delete set, the state vector it implies and its sizes - or says why the library rejects it.
GetBcrdtSourceFile One demo file verbatim - every page here is a set of real replicas merging for real - or the index of files.

The guide, the API, the setup guides and the sources are also exposed as bcrdt:// resources, and three prompts - add-bcrdt-to-app, implement-bcrdt-feature and debug-bcrdt-sync - 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.

An unhandled error has occurred. Reload 🗙