Docs
Cubby stores notes for your agents and gives back the relevant ones when asked. Everything below uses this server's address: https://www.cubby.cash.
Start
- Open the dashboard and create an account. You get an account key (
cubby_acct_…) for the dashboard. Save it; it is shown once. - Add an agent. You get an agent key (
cubby_agent_…). Your agent uses this key; it only reaches that agent's notes. - Connect with MCP, the SDK or HTTP below.
MCP server
Streamable HTTP endpoint at https://www.cubby.cash/mcp. Send the agent key as a Bearer token. Responses are plain JSON; no session is needed.
mcp config
{
"mcpServers": {
"cubby": {
"type": "http",
"url": "https://www.cubby.cash/mcp",
"headers": { "Authorization": "Bearer cubby_agent_..." }
}
}
}With Claude Code:
shell
claude mcp add --transport http cubby https://www.cubby.cash/mcp --header "Authorization: Bearer cubby_agent_..."| Tool | What it does |
|---|---|
remember | Save a note: text, optional subject, tags, ttl_days. |
recall | Most relevant notes for a query; optional subject, tags, limit. |
update_note | Change a note by id. |
forget | Delete a note by id, or all notes for a subject. |
recent_notes | Newest notes first. |
JavaScript SDK
One file, no dependencies. Download cubby.mjs and put it next to your agent.
agent.mjs
import { Cubby } from "./cubby.mjs";
const memory = new Cubby({ key: process.env.CUBBY_AGENT_KEY, baseUrl: "https://www.cubby.cash" });
const note = await memory.remember("Caps any single trade at 0.5 SOL", { subject: userId, tags: ["limits"] });
const { mode, notes } = await memory.recall("how much may I spend for this user?", { subject: userId });
await memory.update(note.id, { text: "Caps any single trade at 1 SOL" });
await memory.forgetSubject(userId);HTTP API
All calls take Authorization: Bearer cubby_agent_… and JSON bodies.
| Call | Body / query |
|---|---|
POST /v1/notes | { text, subject?, tags?, ttl_days? } → { note } |
POST /v1/recall | { query, subject?, tags?, limit? } → { mode, notes } |
GET /v1/notes | ?subject= &tag= &limit= &before= → { notes, next } |
GET /v1/notes/:id | → { note } |
PATCH /v1/notes/:id | { text?, subject?, tags?, ttl_days? } → { note } |
DELETE /v1/notes/:id | → { ok } |
POST /v1/forget | { subject } → { deleted } |
GET /v1/me | Agent name and plan usage. |
shell
curl -s https://www.cubby.cash/v1/recall \
-H "Authorization: Bearer $CUBBY_AGENT_KEY" -H "content-type: application/json" \
-d '{"query":"what do I know about this wallet?","limit":5}'mode is "meaning" when notes were ranked by meaning and "keywords" when only word and subject matching was available. Each note has a score from 0 to 1.
Writing good notes
- One fact per note, in plain words, with the reason: “Avoid: dev wallet sold 40% an hour after launch.”
- Put the exact address, mint or user id in
subject, not only in the text. - Use
ttl_daysfor things that go stale, like a price check. - Update a note when you learn it was wrong instead of adding a second one.
- Never store wallet keys, seed phrases or passwords.
Limits and errors
| Note text | 2,000 characters |
| Subject | 128 characters |
| Tags | 8 per note, 32 characters each |
| Recall | up to 20 notes per call |
| Rate | 600 requests a minute per agent |
Errors look like { "error": { "code", "message" } }. 401 wrong key, 402 plan limit reached (nothing is deleted), 404 no such note, 429 too fast.