kubbi-ai

kubbi is a side-channel for agent payloads — a productized claim-check pattern paired with whatever primary channel you're already using.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Kubbi Inspect: Inspect a kubbi without consuming it. Returns metadata (status, content type, retrieval count, expiry). For multi-file kubbis, also shows the file manifest. Does NOT count as a retrieva
  • Kubbi Claim: Claim a kubbi and retrieve its decrypted content. This COUNTS as a retrieval — if max_retrievals is reached, the content is permanently destroyed afterward. Works for both single-content
  • Kubbi Send: Create a kubbi — an ephemeral, encrypted payload with a unique claim URL. Share the claim URL with any consumer (agent, service, human). The consumer can retrieve the content with no API k

What data it sees

Do you need an account

No: the server works without sign-in

kubbi is a side-channel for agent payloads — a productized claim-check pattern paired with whatever primary channel you're already using. Send a payload via kubbi_send, pass the short claim URL through your MCP tool result, A2A message, queue, or webhook, and the consumer retrieves it with kubbi_claim. Burn-after-read, short TTLs, encryption at rest, and multi-file bundles are defaults, not toggles. Consumer tools (inspect, claim) need no API key — any agent can receive a kubbi with zero setup.

How to connect

How to connect kubbi-ai to Claude

The server address to paste into Claude settings:

https://kubbi-ai--admin-dlwa.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect kubbi-ai to ChatGPT

The server address to paste into ChatGPT settings:

https://kubbi-ai--admin-dlwa.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect kubbi-ai to Cursor

The server address to paste into Cursor settings:

https://kubbi-ai--admin-dlwa.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

kubbi_inspectInspect a kubbi without consuming it. Returns metadata (status, content type, retrieval count, expiry). For multi-file kubbis, also shows the file manifest. Does NOT count as a retrieval — safe to call repeatedly. Accepts a full claim URL or a bare claim token. No API key required.
kubbi_claimClaim a kubbi and retrieve its decrypted content. This COUNTS as a retrieval — if max_retrievals is reached, the content is permanently destroyed afterward. Works for both single-content and multi-file kubbis. Accepts a full claim URL or a bare claim token. No API key required.
kubbi_sendCreate a kubbi — an ephemeral, encrypted payload with a unique claim URL. Share the claim URL with any consumer (agent, service, human). The consumer can retrieve the content with no API key. Requires KUBBI_API_KEY.
kubbi_send_filesCreate a multi-file kubbi package — up to 5 files (5 MB total) encrypted together with a single claim URL. For text files, pass content as a string. For binary files, base64-encode the content and set encoding to 'base64'. Requires KUBBI_API_KEY.
kubbi_getGet detailed metadata for a kubbi you created (by ID). Shows status, retrieval count, timestamps, and whether it has been claimed. Requires KUBBI_API_KEY.
kubbi_deleteDelete (burn) a kubbi you created. Immediately wipes the encrypted payload. Any subsequent claim attempts will receive 410 Gone. Requires KUBBI_API_KEY.