MCP quickstart
Connect your MCP client to the hosted kubbi server and have your agent send and claim its first kubbi. About five minutes.
What you need
- A kubbi API key. Get one from the dashboard after signing up.
- An MCP client. The hosted server speaks the Streamable HTTP transport; stdio is also supported as a fallback.
1. Add kubbi to your MCP client
Paste this config into your client's MCP settings file, replacing kb_... with your real key.
{
"mcpServers": {
"kubbi": {
"url": "https://mcp.kubbi.ai/mcp",
"headers": {
"Authorization": "Bearer kb_..."
}
}
}
}Where to paste it:
- Claude Desktop:
claude_desktop_config.json(Settings → Developer → Edit Config) - Cursor:
.cursor/mcp.jsonin your project root, or globally under Settings → MCP
Restart the client after saving. If your client doesn't speak the Streamable HTTP transport, see the stdio fallback on the MCP Integration reference.
2. Verify the tools loaded
Open a new chat in your client. The agent should now have six kubbi tools available: kubbi_send, kubbi_send_files, kubbi_inspect, kubbi_claim, kubbi_get, kubbi_delete.
Most clients surface a tool list in the chat composer. If kubbi tools don't appear, check that the config file is valid JSON, the URL is exactly https://mcp.kubbi.ai/mcp, and the Bearer token is your real key.
3. Send your first kubbi
Ask the agent in plain language:
Create a kubbi with the content "hello from the agent", a 5-minute TTL,
and a max_retrievals of 1. Print the claim URL.The agent calls kubbi_send and replies with a claim URL like https://api.kubbi.ai/r/abc123xyz. That URL is what you share with the consumer; the payload stays encrypted on kubbi until claimed.
4. Claim it from the other side
The consumer can be another agent, a different MCP client, a curl call, or anything that can make an HTTP request. No API key required to claim.
curl -X POST https://api.kubbi.ai/r/abc123xyz/claimOr, from another MCP-connected agent, simply ask:
Claim the kubbi at https://api.kubbi.ai/r/abc123xyz and show me what is inside.Because max_retrievals was 1, the payload is burned immediately after the first claim. Any follow-up request returns 410 Gone.
Next steps
- The side-channel pattern — the architectural idea kubbi implements.
- Cross-vendor MCP handoff — full example of two vendors' agents exchanging a payload without exposing storage.
- MCP Integration reference — every tool, every parameter, and the stdio fallback config.