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.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 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메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. 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 스타i세 기둥: 리뷰 · 점검 · 사용 정도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