Caib

MCP — assistants wired to the same truth as the API

MCP (Model Context Protocol) is a simple, open way for tools like Claude Desktop, Cursor, and other assistants to call well-defined tools — search a catalogue, fetch a row, start a draft — instead of guessing from a web page. Caib operates an MCP server so your automation stays on the same structured Registry the rest of the product uses — not a scraper’s guess.

What you get

  • Search and read the public catalogue — tools can list and filter what’s on registry.caib.io the same way an HTTP client would: trust tier, optional text q, optional search_payload (whether q also matches JSON payload — see the Registry llms.txt and openapi.json), and clear JSON in the response.
  • Fetch one entity by id — for citations, support, or internal workflows that need a single row.
  • Operator-side drafts (where your setup allows) — when authenticated automation is configured, tools can create manual ingest drafts for review on user.caib.io before anything goes live in the Registry — the same path humans use, not a side channel.

Why we offer it

Generative products keep multiplying. If every assistant has to re-parse HTML, you get drift, errors, and support load. MCP gives integrators a small, standard plug: point the client at our server, set the right hosts and keys for your environment, and the model can ground answers in published catalogue data plus your approved internal workflow — without us inventing a new proprietary plugin for every vendor.

That helps agencies, in-house automators, and power users stay aligned with the HTTP contract (openapi.json) while working inside the tools they already use.

Who it is for

Developers and operators — not your end customers pasting keys into a browser. Technical setup, credentials, and rate limits are the same class of concern as any API integration. If you need a hand or early partner terms, join the waitlist or reach out through the same channels as the rest of Caib.

Where to go next

Registry contract (authoritative): https://registry.caib.io/openapi.json

Product snapshot (human): Now/Next — what we run today and what we’re building toward.

Machine overview: llms.txt for quick orientation; the API remains the source of truth for field names and behaviour.

Join the early access waitlist   Now/Next