Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Turn any OpenAPI/Swagger spec or REST API docs link into a managed MCP server. Free account.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://api.kaiv.ai/api/bridge/manage/mcpターミナルでこれを実行します
claude mcp add --transport http bridge https://api.kaiv.ai/api/bridge/manage/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"bridge": {
"url": "https://api.kaiv.ai/api/bridge/manage/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"bridge": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/manage/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://api.kaiv.ai/api/bridge/manage/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのツール一覧はまだ読み取っていません。エンドポイントは順番にチェックしています。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン kaiv.ai で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(1.0.4)がレジストリに届いたのは16 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, yontu
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
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.
https://api.kaiv.ai/api/bridge/manage/mcp (Streamable HTTP)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".
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.
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.
npx skills add ai-kaiva/bridge
Nothing to install. Node 18+ has everything:
npx @kaiva/bridge help
For a public API spec, one command gives you a working MCP server. No account, no login:
npx @kaiva/bridge try --openapi https://petstore3.swagger.io/api/v3/openapi.json
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 plugin marketplace add ai-kaiva/bridge
claude plugin install kaiva-bridge@kaiva
Or copy just the skill: npx @kaiva/bridge skill install.
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.
claude mcp add postgres -- npx -y @kaiva/postgres-mcp postgresql://localhost/mydb
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.
npx @kaiva/bridge login
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:
export KAIVA_BRIDGE_TOKEN=kv_mgmt_...
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.
# 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
npx @kaiva/bridge push shop-db --db --read-only
npx @kaiva/bridge push handbook --docs ./policies
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 --label --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.
npx @kaiva/bridge skill install # adds the setup skill to Claude Code (~/.claude/skills)
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.
Runnable scripts in examples/:
database-to-claude-code.sh: a Postgres, MySQL or MariaDB database into Claude Codeopenapi-to-cursor.sh: an OpenAPI spec into Cursor for this projectcall-from-your-app.mjs: call your MCP server from your own Node app, no dependencies| Command | What it does | |
|---|---|---|
push --openapi | Create + introspect + expose + publish from an OpenAPI spec | |
push --mcp | Wrap an existing remote MCP server, choosing which of its tools to offer | |
push --postgres | Read-only tools from a Postgres database | |
push --mysql | Read-only tools from a MySQL or MariaDB database | |
push --graphql | Read tools from a GraphQL API's queries (mutations are not offered) | |
push --sqlserver | Read-only tools from a SQL Server or Azure SQL database (sqlserver://… or Server=…;Database=…;User ID=…;Password=…) | |
push --docs | 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 --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 / --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 --client claude-code\ | cursor` | Add a live server to the client's config; --key, --dry-run, --global (Claude Code), --project (Cursor) |
| `uninstall --client claude-code\ | cursor` | Remove it, and revoke a key install added |
doctor [--call ] | 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 | Publish a draft server | |
key [--label L] [--replace] | Mint a server-scoped gateway key (shown once); --replace revokes the earlier key with that label | |
introspect | Re-read the source. Exits 3 if a contract change was held | |
revisions | Contract history: when it changed and which tool | |
promote | Publish the held change | |
reject | Discard it and restore what is being served | |
auto-publish [--off] | Publish contract changes without review | |
invoke [--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).
Call a live example server from your browser, no account needed: https://app.kaiv.ai/try
MIT © SLATEAI LIMITED · kaiv.ai/bridge