Kaiva Bridge

ai.kaiv由 kaiv.ai 發布官方發布者v1.0.4更新於 Oct 24, 2026

Turn any OpenAPI/Swagger spec or REST API docs link into a managed MCP server. Free account.

已驗證Streamable HTTP可網頁執行資料庫知識與記憶開發者工具

服務詳細資訊

識別碼: ai.kaiv/bridge
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 kaiv.ai，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.kaiv%2Fbridge.svg)](https://sourceweft.com/mcp/ai.kaiv%2Fbridge?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

Kaiva Bridge 是託管式 MCP 伺服器，讓助理列出、檢視、草擬並重新整理由 OpenAPI 規格、資料庫或文件產生的託管 MCP 伺服器。

可以做什麼: 列出並檢視 Kaiva Bridge 工作區中的託管 MCP 伺服器
依 OpenAPI 規格連結草擬新的伺服器
在底層 API 變更後重新整理伺服器的工具清單
發布伺服器與逐一開啟工具由使用者在主控台完成
適用情境: 適合想把 API、資料庫或文件集變成託管 MCP 伺服器、又不想手動設定，並想在聊天用戶端裡建立或檢視這些伺服器的情境。發布、金鑰、安裝與稽核日誌由另一個命令列工具負責。
執行需求: 遠端 Streamable HTTP 端點位於 api.kaiv.ai；以 OAuth 2.1 使用免費 Kaiva Bridge 帳號登入，無需複製金鑰。命令列工具需要 Node 18+，用於 CI 時需在 KAIVA_BRIDGE_TOKEN 提供 Management 金鑰。

安裝前請注意

此連接器只負責草擬與列出，發布和開啟工具要在主控台完成，請確認最後曝露的內容。命令列工具可曝露寫入類操作、在略過憑證檢查的情況下連線資料庫，並產生只顯示一次的伺服器專屬金鑰；安裝技能會在這些步驟前詢問。Management 金鑰與 gateway 金鑰不可互換。

安裝

在 SourceWeft 中

開啟儀表板中的 Kaiva Bridge，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.kaiv%2Fbridge/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "kaiva-bridge": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/manage/mcp"
    }
  }
}

README

Kaiva Bridge

Kaiva Bridge turns your API, database or documents into a managed MCP server that Claude, ChatGPT, Cursor, VS Code and other AI clients can use. This page covers the Kaiva Bridge connector, ai.kaiv/bridge, first; the command-line tool follows.

Kaiva Bridge as an MCP connector (`ai.kaiv/bridge`)

Kaiva Bridge is also an MCP server itself, so your AI client can create and manage MCP servers from inside a chat. It is listed in the official MCP Registry as ai.kaiv/bridge and in Claude's connector directory.

Address: https://api.kaiv.ai/api/bridge/manage/mcp (Streamable HTTP)
Sign-in: OAuth 2.1 with your Kaiva Bridge account (free, no card). No key to copy.
Tools: list_my_servers, get_server, create_server (drafts a server from an OpenAPI spec URL) and reintrospect_server (refreshes a server's tools when the API changes).

The connector drafts and lists. Publishing a server and switching its tools on happen in the console, by you.

VS Code and GitHub Copilot: click Add to VS Code on kaiv.ai/bridge, or run MCP: Add Server in VS Code with the address above, then sign in when asked. Claude: claude.ai/directory/kaiva-bridge. Claude Code: claude mcp add --transport http --scope user kaiva-bridge https://api.kaiv.ai/api/bridge/manage/mcp. Cursor and ChatGPT: the Add menu on kaiv.ai/bridge.

Then ask: "List my Kaiva Bridge servers" or "Create a Kaiva Bridge server from https://petstore3.swagger.io/api/v3/openapi.json".

The command-line tool

Publish any API or database as a live MCP server, from your terminal.

Kaiva Bridge turns an OpenAPI spec, a database (PostgreSQL, MySQL, MariaDB or SQL Server) or a remote MCP server into a managed MCP server your agents can call. This CLI drives it over the Management API. Every setup command is safe to run again.

For your coding agent

Connect your AI agent to APIs, databases and documents with Kaiva Bridge. 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.

Install

Nothing to install. Node 18+ has everything:

Try it with no account

For a public API spec, one command gives you a working MCP server. No account, no login:

You get the server's address, a key for that one server, and a claim link. The server offers only the spec's GET operations, and lasts 72 hours or 500 calls. Open the claim link to keep it in your workspace: it keeps its address and your plan's limits apply. The key stops working at claim, so connect your AI client again from the console. Then you can add an API key and switch on other operations. Coding agents can do this themselves (--json prints one JSON object).

In a cloud agent sandbox (Codex cloud, Claude Code on the web), allow the domains api.kaiv.ai and registry.npmjs.org first: their network access is off or limited by default.

Claude Code plugin

Or copy just the skill: npx @kaiva/bridge skill install.

Postgres on your machine, no account

For a Postgres database that only the AI clients on your machine use, Kaiva Postgres MCP is a free, open-source MCP server that runs locally and only reads. It replaces the archived @modelcontextprotocol/server-postgres: change the package name and nothing else changes.

bash

claude mcp add postgres -- npx -y @kaiva/postgres-mcp postgresql://localhost/mydb# or, from the same plugin marketplace as above (reads DATABASE_URL from your environment)claude plugin install postgres-mcp@kaiva

claude mcp add postgres -- npx -y @kaiva/postgres-mcp postgresql://localhost/mydb# or, from the same plugin marketplace as above (reads DATABASE_URL from your environment)claude plugin install postgres-mcp@kaiva

When you need the same database in Claude.ai or ChatGPT, or for your team, push --db below serves it from Bridge.

Auth

The terminal shows a code and opens the console. Enter the code there and approve it (owner or admin of the workspace). The key is saved for this machine in ~/.config/kaiva-bridge/credentials.json, readable only by you. whoami shows the workspace and key in use; logout revokes the key and removes it.

For CI and scripts, use a Management key from the console (Keys & access, key type Management) instead. When set, it is used in place of a saved login:

logout revokes only a saved login. A key you supply in KAIVA_BRIDGE_TOKEN is yours to manage: unset it, and revoke it in the console when it is no longer needed. Signing in again revokes the login it replaces.

Management keys are refused by the MCP gateway, and gateway keys are refused by the Management API: the two credential types are never interchangeable.

Quickstart: source to live server

bash

# An API spec (only operations that read are exposed with --read-only)npx @kaiva/bridge push my-api --openapi https://api.example.com/openapi.json --read-only
# A database: DATABASE_URL from the environment or .env; Postgres, MySQL, MariaDB or SQL Servernpx @kaiva/bridge push shop-db --db --read-only# → LIVE  https://api.kaiv.ai/api/bridge/mcp/shop-db-a1b2c3d4# → check  first call: get_orders answered in 84ms (and what the AI is given)
# Documents: PDF, Word, PNG, JPEG, text or Markdown files, or a folder of themnpx @kaiva/bridge push handbook --docs ./policies# waits until each file is read, then → LIVE  https://api.kaiv.ai/api/bridge/mcp/handbook-a1b2c3d4
npx @kaiva/bridge install my-api --client claude-code   # or --client cursor

# An API spec (only operations that read are exposed with --read-only)npx @kaiva/bridge push my-api --openapi https://api.example.com/openapi.json --read-only
# A database: DATABASE_URL from the environment or .env; Postgres, MySQL, MariaDB or SQL Servernpx @kaiva/bridge push shop-db --db --read-only# → LIVE  https://api.kaiv.ai/api/bridge/mcp/shop-db-a1b2c3d4# → check  first call: get_orders answered in 84ms (and what the AI is given)
# Documents: PDF, Word, PNG, JPEG, text or Markdown files, or a folder of themnpx @kaiva/bridge push handbook --docs ./policies# waits until each file is read, then → LIVE  https://api.kaiv.ai/api/bridge/mcp/handbook-a1b2c3d4
npx @kaiva/bridge install my-api --client claude-code   # or --client cursor

install adds the server to Claude Code (this folder's .mcp.json, or --global) or Cursor (~/.cursor/mcp.json, or --project), keeping every other entry. The client signs in with your Kaiva account the first time; --key writes a key for this one server instead. --dry-run shows the change; uninstall removes it. For any other MCP client, key <server-id> --label <client> --replace makes a gateway key to paste with the endpoint. Run the same commands again and nothing is duplicated: push reuses the server with that name, install leaves an existing entry as it is, and key --replace swaps the key with that label.

Let your coding agent do it

Then ask: "connect my database to Claude Code with Kaiva Bridge". The skill runs the commands below, asks you before connecting without certificate checks or exposing operations that write, and confirms with a first tool call.

Examples

Runnable scripts in examples/:

database-to-claude-code.sh: a Postgres, MySQL or MariaDB database into Claude Code
openapi-to-cursor.sh: an OpenAPI spec into Cursor for this project
call-from-your-app.mjs: call your MCP server from your own Node app, no dependencies

Commands

Command	What it does
`push <name> --openapi <url>`	Create + introspect + expose + publish from an OpenAPI spec
`push <name> --mcp <url>`	Wrap an existing remote MCP server, choosing which of its tools to offer
`push <name> --postgres <conn>`	Read-only tools from a Postgres database
`push <name> --mysql <conn>`	Read-only tools from a MySQL or MariaDB database
`push <name> --graphql <endpoint>`	Read tools from a GraphQL API's queries (mutations are not offered)
`push <name> --sqlserver <conn>`	Read-only tools from a SQL Server or Azure SQL database (`sqlserver://…` or `Server=…;Database=…;User ID=…;Password=…`)
`push <name> --docs <files or folders>`	Documents your AI can search and read, page by page; the same file name again replaces that document. `--no-wait` returns once the files are sent
`push <name> --db [--db-env NAME]`	The database in `DATABASE_URL` (or NAME), from the environment or `.env.local`/`.env`; the engine is told apart by the address, which never appears on the command line
`push … --read-only`	Expose only operations that read; writes stay off until you choose them
`push … --no-check`	Skip the setup check every `push` and `try` ends with: one real call, writes switched on, the tool list's size and tables that look private
`push … --ca-file <pem>` / `--no-verify-tls`	A database with a self-signed certificate: check it against your provider's CA, or connect without checking
`login [--no-browser]`	Approve this machine in the console and save a key for it
`whoami`	The workspace, account and key in use
`logout`	Revoke this machine's key and remove it
`skill install [--project]`	Add the setup skill for coding agents
`install <server> --client claude-code\|cursor`	Add a live server to the client's config; `--key`, `--dry-run`, `--global` (Claude Code), `--project` (Cursor)
`uninstall <server> --client claude-code\|cursor`	Remove it, and revoke a key `install` added
`doctor <server> [--call <tool>]`	Check reachability, sign-in, publication, the MCP handshake and tool list; each step passes, fails with a code and a fix, or says it did not run. `--call` makes one call with a tool that reads. Ends with a receipt for support (no secrets)
`servers`	List servers with state and source
`publish <server-id>`	Publish a draft server
`key <server-id> [--label L] [--replace]`	Mint a server-scoped gateway key (shown once); `--replace` revokes the earlier key with that label
`introspect <server-id>`	Re-read the source. Exits 3 if a contract change was held
`revisions <server-id>`	Contract history: when it changed and which tool
`promote <server-id>`	Publish the held change
`reject <server-id>`	Discard it and restore what is being served
`auto-publish <server-id> [--off]`	Publish contract changes without review
`invoke <server-id> <tool-id> [--args '{"k":"v"}']`	Test-call a tool through the real governed path (audited)
`logs [--limit 50]`	Tail the audit log
`metrics [--range 24h]`	Workspace KPIs (1h · 24h · 7d · 30d)

--json on push, key, install, whoami and doctor prints one JSON result on stdout (progress goes to stderr), for scripts and agents. KAIVA_BRIDGE_URL overrides the API base (defaults to https://api.kaiv.ai/api/bridge/v1).