MCP
Give your agents secure handoffs with a single MCP tool
kubbi is an MCP-compatible tool server. Install it once and every agent in your stack can send single payloads or multi-file packages, claim, inspect, and manage temporary encrypted handoffs — no SDK wiring required.
Six tools, complete handoff control
Every tool your agents need to send single payloads or multi-file packages, retrieve, preview, and manage temporary encrypted handoffs.
Parameters
contentcontentTypettlSecondsmaxRetrievalsmetadataReturns
claim URL + kubbi ID
Parameters
filesttlSecondsmaxRetrievalsmetadataReturns
claim URL + kubbi ID + file count
Parameters
claimUrlReturns
decrypted content (or all files for packages)
Parameters
claimUrlReturns
metadata (status, content type, retrieval count, expiry, file manifest for packages)
Parameters
idReturns
full kubbi detail JSON
Parameters
idReturns
confirmation
Install and configure
Add kubbi to your MCP client in one step. Paste the config below and replace the API key with your own.
Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"kubbi": {
"command": "npx",
"args": ["-y", "@kubbi.ai/mcp"],
"env": {
"KUBBI_API_KEY": "kb_..."
}
}
}
}Cursor
.cursor/mcp.json
{
"mcpServers": {
"kubbi": {
"command": "npx",
"args": ["-y", "@kubbi.ai/mcp"],
"env": {
"KUBBI_API_KEY": "kb_..."
}
}
}
}Get your API key from the dashboard. The server runs via npx — no global install needed.
Talk to your agent like normal
Once kubbi is connected, your agent discovers the tools automatically. Just describe what you need in plain language.
“Create a kubbi with this analysis result and send me the claim URL.”
“Bundle these three files into a package kubbi and give me the claim link.”
“Claim the payload at this URL and summarize what’s inside.”
“Store this API response as a kubbi with max_retrievals: 1 and a 1-hour TTL.”
“Inspect the kubbi at this claim URL before I claim it.”
“Delete the kubbi I just created — I changed my mind.”
Why secure handoffs matter for MCP
Without kubbi, agents inline sensitive payloads directly into tool outputs, prompts, and orchestrator state. That data gets logged, cached, and replayed across every hop in the workflow.
With kubbi, the agent stores the payload once and passes only a claim URL. The next agent or human claims it on their own schedule. The payload is encrypted, time-limited, and can self-destruct after a single read.
The result: sensitive data stops traveling through your entire tool chain. Only the link moves.
Built-in protections
Encrypted at rest
AES-256-GCM encryption before the payload touches storage.
TTL expiry
Every kubbi self-destructs on schedule — no stale data, no cleanup.
Burn after read
One claim, one read, gone. Ideal for secrets and one-time handoffs.
Inspect before claim
Preview metadata without consuming the payload so the agent knows what it’s getting.
Try kubbi on your next workflow
Create a temporary handoff, pass one claim URL, and let the next agent or human pick it up when ready.