Connect
Paste a Postgres connection string or an OpenAPI URL. Kaiva introspects the schema and proposes tools.
Paste an OpenAPI spec or connect Postgres. Kaiva generates the tools and gives you one live URL for Cursor, Claude Code, or any other app - in minutes, with no code or infrastructure.
3 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>An 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 Postgres connection string or an OpenAPI URL. Kaiva introspects the schema and proposes tools.
Kaiva writes the tools, names, descriptions, input schemas. You pick which ones are exposed, and nothing goes live until you say so.
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.
ILLUSTRATIVE EXAMPLE
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 above ↑VERSIONS · endoflife.date
Latest versions, LTS windows and end-of-life dates for 300+ products.
Open in the sandbox →DNS · Google Public DNS
Live DNS records, TTLs, reverse lookups and DNSSEC.
Open in the sandbox →EMAIL · 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 sandbox →IMAGES · Docker Hub
Does this image:tag exist, how big is it, and which platforms does it cover?
Open in the sandbox →STATUS · public status pages
Is a service you depend on down, or is it you? Fifteen providers, with a verdict.
Open in the sandbox →BROWSERS · caniuse.com
Which browsers support a web feature, and from which version.
Open in the sandbox →No. Bridge hosts the server. You get an endpoint on api.kaiv.ai and a key; your API or database stays where it is.
Sign up, paste a spec URL or a Postgres connection string, pick the tools, publish. No card, no server to run.
FREE PLAN · 3 SERVERS · 3 TEAM MEMBERS · 200K TOOL CALLS / MO · NO CARD