# Kaiva > Kaiva (SLATEAI LIMITED, London) builds AI infrastructure that connects agents > to real systems. Bridge is its lead product: APIs, databases, spreadsheets and > documents become hosted MCP servers. Our approach explains the domain experience > and principles behind it. Kaiva Bridge accepts an OpenAPI (3.x) or Swagger (2.0) spec (or, with no spec, a cURL command or a Postman collection), a GraphQL API, a database (PostgreSQL, MySQL, MariaDB or SQL Server), a spreadsheet (CSV), documents (PDF, Word, PNG, JPEG, text or Markdown) or an existing remote MCP server, and returns a hosted MCP endpoint. It is listed in Claude's connector directory, where Claude can create a server from a spec link inside a chat. Tools are generated from the source by introspection (read-only from the database schema) and exposed individually; nothing is reachable until it is published. Upstream credentials stay server side and are never returned to the calling agent. There is no server code to write and nothing to host. The free tier is 3 servers, 200,000 tool calls per month and 200 pages of documents, no card. Registry name: `ai.kaiv/bridge`. ## For AI agents: create a server with no account An agent can create a working MCP server from a PUBLIC OpenAPI or Swagger spec itself, with no account and no login, then hand its person a claim link: POST https://api.kaiv.ai/api/bridge/claimable Content-Type: application/json {"specUrl": "https://example.com/openapi.json", "name": "my-api"} (or `"spec": ""` instead of `specUrl`). The response has `mcpUrl`, `apiKey` (shown once; send it as `Authorization: Bearer `), `claimUrl`, `expiresAt` and `tools`. The server offers only the spec's GET operations and lasts 72 hours or 500 calls. Give the person the `claimUrl`: claiming keeps the server in their workspace at the same address, under their plan's limits. The `apiKey` stops working at claim; the person connects their AI client again from the console. They can then add the API's key and switch on other operations. Do not send credentials; they are refused. The same from a terminal: `npx @kaiva/bridge try --openapi --json`. The full recipe in the auth.md format (provision, use, claim, every refusal): https://kaiv.ai/bridge/auth.md In Claude Code, the Kaiva Bridge plugin teaches the agent this flow: `claude plugin marketplace add ai-kaiva/bridge`, then `claude plugin install kaiva-bridge@kaiva`. Install the Kaiva Bridge skill in Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and other coding agents: `npx skills add ai-kaiva/bridge`. In a cloud sandbox (Codex cloud, Claude Code on the web), allow the domains `api.kaiv.ai` and `registry.npmjs.org` first. ## Kaiva Bridge - [Bridge overview](https://kaiv.ai/bridge): what it does, the sources it accepts (APIs, databases, spreadsheets, documents and remote MCP servers), and how the gateway works. - [Docs](https://kaiv.ai/bridge/docs): quickstart, connecting a client, limiting what an agent can call, and the Management API reference. - [Pricing](https://kaiv.ai/bridge/pricing): Free, Pro and Enterprise, with limits stated per plan. - [Security](https://kaiv.ai/bridge/security): the controls in production today, plus an honest compliance status: GDPR aligned, SOC 2 Type II in progress and not yet certified, ISO 27001 planned. - [Status](https://kaiv.ai/bridge/status): live uptime and incident history, independently monitored. - [Changelog](https://kaiv.ai/bridge/changelog): every release, newest first. ## Guides - [How to convert an API into an MCP server](https://kaiv.ai/bridge/guides/convert-api-to-mcp): OpenAPI or Swagger (or a cURL command or Postman collection) to a hosted MCP server, from the console, the CLI or inside Claude. - [How to turn a Postgres, MySQL or SQL Server database into an MCP server](https://kaiv.ai/bridge/guides/database-to-mcp): read-only tools from PostgreSQL, MySQL, MariaDB or SQL Server. - [How to make your documents searchable by AI with an MCP server](https://kaiv.ai/bridge/guides/documents-to-mcp): PDFs, Word files, images and notes as search tools. - [How to turn a spreadsheet into an MCP server](https://kaiv.ai/bridge/guides/spreadsheet-to-mcp): a CSV from Excel or Google Sheets as tools your AI can query. - [How to add an MCP server to Claude, ChatGPT and Cursor](https://kaiv.ai/bridge/guides/add-mcp-server-to-claude-chatgpt-cursor): client by client, with sign-in instead of keys. - [How to host a remote MCP server without running one](https://kaiv.ai/bridge/guides/host-remote-mcp-server): a hosted Streamable HTTP endpoint for any source. - [How to add WebMCP to your website](https://kaiv.ai/bridge/guides/add-webmcp-to-your-website): let AI agents in the browser use the tools you make public, with one snippet (WebMCP support is in beta). ## Using Bridge - CLI: `npx @kaiva/bridge try --openapi ` needs no account (a server with the spec's GET operations for 72 hours, plus a claim link). `npx @kaiva/bridge login` approves the machine in the console, then `npx @kaiva/bridge push --openapi `, also `--postgres `, `--mysql ` (MySQL and MariaDB), `--docs ` and `--mcp `. `install --client claude-code|cursor` adds a live server to the client's config, and `doctor ` checks each step of a connection and says what to fix. Setup commands are safe to run again; `--read-only` exposes only operations that read. For coding agents: `npx @kaiva/bridge skill install` adds a setup skill to Claude Code. MIT licensed, [source on GitHub](https://github.com/ai-kaiva/bridge), [package on npm](https://www.npmjs.com/package/@kaiva/bridge). - WebMCP support (beta): a server's Connect tab, Your website (WebMCP), generates code for your web page so AI agents in the browser can call the tools you make public. Website keys are public by design and reach only the tools made public on them; only tools that read can be public. - Gateway endpoints are `https://api.kaiv.ai/api/bridge/mcp/` over streamable HTTP. - Authentication is a scoped gateway key, or OAuth 2.1 with dynamic client registration. Discovery follows RFC 9728 and RFC 8414. - In CI and scripts, set `KAIVA_BRIDGE_TOKEN` to a management key minted in the console under Keys & access; on a workstation, `login` saves a key for that machine. ## Our approach - [Our approach](https://kaiv.ai/approach): how experience with agents and business workflows, finance operations among them, and with operational controls informs Kaiva’s AI infrastructure. Bridge is the available self-serve product; specific applied-agent projects are discussed directly. ## Company and policies - [About](https://kaiv.ai/about): SLATEAI LIMITED, Company No. 16601902, London. - [Privacy](https://kaiv.ai/privacy), [Terms](https://kaiv.ai/terms), [Data Processing Agreement](https://kaiv.ai/dpa). - [Security contact](https://kaiv.ai/.well-known/security.txt): security@kaiv.ai, RFC 9116. - [Blog](https://kaiv.ai/blog), [Contact](https://kaiv.ai/contact).