Connect
Paste a database connection string or an OpenAPI URL, or drop in your documents. Kaiva reads the source and proposes tools.
Paste an OpenAPI spec, connect a database or drop in your documents. Get one MCP URL for Claude, ChatGPT, Cursor, VS Code and any other AI client, in minutes. No code to write, no infrastructure to maintain. Free to start.
10 servers, 200,000 tool calls a month, 3 seats, no card. Four things that are true on the free plan, not four steps to follow.
No card, no clock, no downgrade email. Most builders never leave it.
npx @kaiva/bridge push my-api --openapi <spec-url>Install the skill so your coding agent can set up managed MCP connections for you. Try public APIs without an account. Works with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and other compatible coding agents.
npx skills add ai-kaiva/bridgeAn example server we published from a public API. Read-only, and anyone can call it with no account and no key. Every server you publish gets an endpoint that works exactly like this one.
01 ECOSYSTEM
02 PACKAGE
THIS CALLS THE REAL GATEWAY, RUN IT
READ-ONLY · RATE-LIMITED · NO KEY
Point Kaiva at a source, choose what an agent may call, and hand the endpoint to any MCP client.
Paste a database connection string or an OpenAPI URL, or drop in your documents. Kaiva reads the source and proposes tools.
Kaiva writes the tools, names, descriptions, input schemas. You pick which ones are exposed. Every tool starts switched off, and database servers can only read.
3 OF 4 TOOLS EXPOSED
Copy the config into Cursor, Claude Code, or your own SDK client. Every call it makes lands in your audit log.
Streamable HTTP with bearer keys, or OAuth 2.1 sign-in on every plan.
https://api.kaiv.ai/api/bridge/mcp/your-serverFor Claude Code, run claude mcp add.
Replace the sample endpoint and key with the values from your server in the console.
3–7×
Kaiva generates leaner tool definitions than hand-written ones, so agents spend less context reloading them and less of every request goes on overhead. It also shows which tools your agent has never called, so you can switch them off.
Access is per tool, not per server, so you ship the reads now without exposing forty endpoints you have not reviewed. Every call is logged with its arguments, result and latency.
tool not in allowed set for key kv_live_…9pKd · policy: your-server/read-only
Each was built the way yours will be: point Bridge at a public API, pick the tools, publish.
SECURITY · deps.dev (Google)
Trust-check any dependency: versions, licenses, CVEs, OpenSSF Scorecard.
Run it aboveVERSIONS · endoflife.date
Latest versions, LTS windows and end-of-life dates for 300+ products.
Open in the sandboxDNS · Google Public DNS
Live DNS records, TTLs, reverse lookups and DNSSEC.
Open in the sandboxEMAIL · live DNS (MX, SPF, DMARC)
Can a domain receive mail, and can it be spoofed? MX, SPF and DMARC, with a verdict.
Open in the sandboxIMAGES · Docker Hub
Does this image:tag exist, how big is it, and which platforms does it cover?
Open in the sandboxSTATUS · public status pages
Is a service you depend on down, or is it you? Fifteen providers, with a verdict.
Open in the sandboxBROWSERS · caniuse.com
Which browsers support a web feature, and from which version.
Open in the sandboxNo. Bridge hosts the server. You get an endpoint on api.kaiv.ai that AI clients sign in to with your account or reach with a key; your API or database stays where it is.
A database (PostgreSQL, MySQL, MariaDB or SQL Server), any OpenAPI or Swagger spec, a GraphQL API, a spreadsheet (CSV), a set of documents (PDF, Word, images or text), or a remote MCP server you want behind one endpoint. Paste the connection string or the spec URL and Bridge introspects it and proposes the tools; drop in documents and Bridge makes them searchable.
Yes. Paste a cURL command or upload a Postman collection (v2.0 or v2.1). Bridge reads it in your browser, turns each request into a tool and shows you what it will import, and what it can't, before anything is created.
Yes, for a public API spec. The agent runs npx @kaiva/bridge try --openapi <spec-url> and gets a server with the spec's GET operations for 72 hours plus a claim link for you. Claim it to keep it in your workspace.
Yes. WebMCP support is in beta. With WebMCP, a new browser standard (in Chrome so far), your website can offer tools to the AI agent in a visitor's browser. Open a server's Connect tab, choose Your website (WebMCP), pick the tools to make public, list your sites and paste the code into your page. The key in that code is public, so it reaches only the tools you chose, and only tools that read can be public.
10 MCP servers, 200,000 tool calls a month, 200 pages of documents, 3 team members, no card. It does not expire, and hosting is included.
Claude (Kaiva Bridge is in Claude's connector directory), ChatGPT, Cursor, Claude Code, VS Code and anything else that speaks MCP over Streamable HTTP, including the official TypeScript and Python SDKs.
Yes. Every tool starts switched off, and you switch it on tool by tool. Database, spreadsheet and document servers can only read: their queries run in read-only transactions, so a tool call cannot change your data. Ship the reads today and add writes once you have reviewed them.
It is encrypted at rest with AES-256-GCM, decrypted only inside a request, and never returned by the API or the console.
Yes, MIT-licensed on GitHub and published to npm as @kaiva/bridge. The hosted gateway is not.
Self-hosting (on-prem or your own cloud) is an Enterprise option. Free and Pro are hosted.
Sign up, then paste a spec URL, connect a database or drop in your documents, and publish. No card, no server to run.
FREE PLAN · 10 SERVERS · 3 TEAM MEMBERS · 200K TOOL CALLS / MO · NO CARD