=============== LIBRARY RULES =============== From library maintainers: - To create a live MCP server from a public OpenAPI or Swagger spec with no account, run: npx @kaiva/bridge try --openapi (add --json for machine-readable output). - Without the CLI, send POST https://api.kaiv.ai/api/bridge/claimable with JSON {"specUrl": ""} or {"spec": ""}. The answer has mcpUrl, apiKey (shown once, sent as Authorization: Bearer ), claimUrl, expiresAt and tools. - A server created without an account offers only the spec's GET operations, accepts no credentials, and lasts 72 hours or 500 tool calls. Never send credentials to it; they are refused. - Always give the user the claimUrl. Claiming keeps the server in their Kaiva Bridge workspace at the same address, under their plan; the apiKey stops working then, and they connect their AI client again from the server's Connect tab. - For private APIs, databases, documents or tools that change data, sign in first: npx @kaiva/bridge login, then npx @kaiva/bridge push --openapi (or --postgres, --mysql, --docs, --mcp). - In a cloud agent sandbox such as Codex cloud or Claude Code on the web, allow the domains api.kaiv.ai and registry.npmjs.org before running these commands. ### Install the Kaiva Bridge setup skill for Claude Code Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Run this command to add the setup skill to Claude Code's skills directory (~/.claude/skills). After installation, you can ask the agent to connect a database to Claude Code with Kaiva Bridge. ```bash npx @kaiva/bridge skill install # adds the setup skill to Claude Code (~/.claude/skills) ``` -------------------------------- ### Show @kaiva/bridge help Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Displays help for the @kaiva/bridge CLI. Requires Node 18+ and npx; no installation needed. ```bash npx @kaiva/bridge help ``` -------------------------------- ### Install Kaiva Bridge for Claude Code or Cursor Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Run these commands to install the Kaiva Bridge server for Claude Code or Cursor. The command writes the client's own config, preserves other entries, and is idempotent. Use --global for all projects with Claude Code, --project for Cursor's project config. Without --key, the client prompts for sign-in; with --key, a gateway key is written (not with --global). --dry-run shows the change first. ```bash npx -y @kaiva/bridge install --client claude-code # this folder's .mcp.json (--global: all projects) npx -y @kaiva/bridge install --client cursor # ~/.cursor/mcp.json (--project: .cursor/mcp.json) ``` -------------------------------- ### Push API spec, database, and documents to live server Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Pushes an OpenAPI spec (read-only), a MySQL database (connection string from stdin, read-only), and a folder of documents to live MCP servers. The `install` command adds the server to Claude Code or Cursor. `push` reuses the server with that name; `install` leaves existing entries; `key --replace` swaps keys. ```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 ``` ```bash # A database: the connection string comes from stdin, not the command line printf %s "$DATABASE_URL" | npx @kaiva/bridge push shop-db --mysql --secret-stdin --read-only # → LIVE https://api.kaiv.ai/api/bridge/mcp/shop-db-a1b2c3d4 ``` ```bash # Documents: PDF, Word, PNG, JPEG, text or Markdown files, or a folder of them npx @kaiva/bridge push handbook --docs ./policies # waits until each file is read, then → LIVE https://api.kaiv.ai/api/bridge/mcp/handbook-a1b2c3d4 ``` ```bash npx @kaiva/bridge install my-api --client claude-code # or --client cursor ``` -------------------------------- ### Install Kaiva Bridge plugin for Claude Code Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Adds the ai-kaiva/bridge marketplace and installs the kaiva-bridge@kaiva plugin. Alternatively, copy just the skill with `npx @kaiva/bridge skill install`. ```bash claude plugin marketplace add ai-kaiva/bridge claude plugin install kaiva-bridge@kaiva ``` -------------------------------- ### Try a public API without an account Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Creates a live MCP server from a public OpenAPI spec without an account or login. The server offers only GET operations, lasts 72 hours or 500 calls, and provides a claim link to keep it in your workspace. The key stops working at claim, so reconnect your AI client. Use --json to get a single JSON object. In cloud agent sandboxes, allow api.kaiv.ai and registry.npmjs.org domains first. ```bash npx @kaiva/bridge try --openapi https://petstore3.swagger.io/api/v3/openapi.json ``` -------------------------------- ### Try a public API spec without an account: npx -y @kaiva/bridge try Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Creates a hosted MCP server for a public API spec with no account or login. The resulting server exposes only the spec's GET operations, lasts 72 hours or 500 calls, and returns a claim link the user opens to keep it. Run it again safely; the same server name is reused and --replace keeps one key per client. ```bash npx -y @kaiva/bridge try --openapi https://petstore.swagger.io/v2/swagger.json ``` -------------------------------- ### Login to Kaiva Bridge Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Starts the login flow. The terminal shows a code and opens the console; enter the code and approve it as owner or admin. The key is saved to `~/.config/kaiva-bridge/credentials.json` readable only by you. `whoami` shows the workspace and key; `logout` revokes the key. ```bash npx @kaiva/bridge login ``` -------------------------------- ### Add the Kaiva Bridge skill for coding agents Source: https://github.com/ai-kaiva/bridge/blob/main/README.md Installs the Kaiva Bridge skill so coding agents like Claude Code, Codex, Cursor, Gemini CLI, and GitHub Copilot can set up hosted MCP connections. Requires Node 18+ and npx. ```bash npx skills add ai-kaiva/bridge ``` -------------------------------- ### Push OpenAPI spec server with --openapi Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Creates or updates a server from an OpenAPI specification URL. The --read-only flag exposes only GET operations; writes stay off. The last line of output is a JSON object with id, endpoint, slug, tools, exposed, writesLeftOff, reused, and held. ```bash npx -y @kaiva/bridge push petstore --openapi https://example.com/openapi.json --read-only --json ``` -------------------------------- ### List server tools with tools Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Lists the tools exposed by a server. Use it when the user wants to enable write operations; let the user choose them in the console (Servers → the server → Tools). Never expose writes on your own. ```bash npx @kaiva/bridge tools ``` -------------------------------- ### Push documents server with --docs Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Pushes a documents server from a folder of PDF, Word, PNG, JPEG, text, or Markdown files. The command waits until every file is read; the server goes live with its first ready document. Documents expose AI search and page-reading tools only, so --read-only does not apply. ```bash npx -y @kaiva/bridge push handbook --docs ./policies --json ``` -------------------------------- ### Confirm bridge works with @kaiva/bridge tools and invoke Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Verify a bridge server is working. The first command lists exposed tools; the second invokes a tool with empty arguments. Pick a read tool with no required inputs, such as a database get_ with no filters, then report the endpoint, tool count, and the first call's result. A new client may need restarting before it lists the tools. ```bash npx -y @kaiva/bridge tools npx -y @kaiva/bridge invoke --args '{}' ``` -------------------------------- ### VS Code Configuration (.vscode/mcp.json) Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Add the Kaiva Bridge server to VS Code's .vscode/mcp.json. Replace , , and with your values. Ensure this file is in .gitignore to avoid committing the key. ```json { "servers": { "": { "type": "http", "url": "", "headers": { "Authorization": "Bearer " } } } } ``` -------------------------------- ### Codex Configuration (config.toml) Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Add the Kaiva Bridge server to Codex's ~/.codex/config.toml. Replace , , and with your values. The key is shown once and should be placed here. ```toml [mcp_servers.] url = "" http_headers = { "Authorization" = "Bearer " } ``` -------------------------------- ### Generate a Key for Other Clients Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Creates a gateway key for a client like Codex, VS Code, or my-app. Use one label per client. --replace revokes the earlier key with that label for this server, leaving one key. The key is shown only once; put it directly into the client configuration and do not echo it. ```bash npx -y @kaiva/bridge key --label codex --replace --json ``` -------------------------------- ### Promote held tool with promote Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Releases a tool that was held for review after a push exited with code 3. Agents keep the previous definitions until the user runs this command. ```bash npx @kaiva/bridge promote ``` -------------------------------- ### Push MySQL database server with --secret-stdin Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Pushes a MySQL database server using a connection string from the DATABASE_URL environment variable. The connection string is piped via stdin with --secret-stdin so it never appears in the command line or output. Always include --read-only to expose only read operations. ```bash printf %s "$DATABASE_URL" | npx -y @kaiva/bridge push shop-db --mysql --secret-stdin --read-only --json ``` -------------------------------- ### Check CLI sign-in with whoami Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Checks whether the CLI is signed in. If it reports not signed in, the user must run npx @kaiva/bridge login in their own terminal and approve the code in the browser (owner or admin required). In CI, KAIVA_BRIDGE_TOKEN holds a management key instead. ```bash npx @kaiva/bridge whoami ``` -------------------------------- ### Set management key for CI Source: https://github.com/ai-kaiva/bridge/blob/main/README.md For CI and scripts, use a Management key from the console (Keys & access, key type Management). When set, it is used in place of a saved login. `logout` revokes only a saved login; the key in `KAIVA_BRIDGE_TOKEN` is managed by you. ```bash export KAIVA_BRIDGE_TOKEN=kv_mgmt_... ``` -------------------------------- ### Use --no-verify-tls to skip certificate check Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Flag to add to a push command when Bridge cannot verify the database's certificate. It connects without checking the certificate (still encrypted). Ask the user which option they want; do not choose for them. ```bash --no-verify-tls ``` -------------------------------- ### Use --ca-file for certificate verification Source: https://github.com/ai-kaiva/bridge/blob/main/skills/kaiva-bridge/SKILL.md Flag to add to a push command when Bridge cannot verify the database's certificate. It checks the certificate against the provider's CA (preferred; most hosted providers publish one). Ask the user which option they want; do not choose for them. ```bash --ca-file ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.