An API as an MCP server

Give Bridge an OpenAPI 3 spec and it hosts an MCP server with one tool per operation. Your API's credentials stay with Bridge; your AI only gets the tools.

Add your spec

In the console, choose New server → API. Link the spec by URL, paste it, or upload the file, so a spec with no public URL works too. From a terminal:

npx @kaiva/bridge push my-api --openapi https://api.example.com/openapi.json --read-only

What your AI gets

One tool per operation, keeping the spec's descriptions and parameter rules. You choose which operations are exposed. From the CLI, --read-only exposes only the operations that read, and the rest stay off until you choose them.

Your API's credentials

Add a bearer token, a basic login, or an API key sent as a header or query parameter. It is stored encrypted and sent only to your API.

When the API changes

Re-read the spec from the server's page, or with kaiva-bridge introspect. A tool whose meaning changed is held until you publish or reject the change, so your AI keeps the version it had.