MCP + HTTP · free · no sign-up wall

Give your AI agent a memory.

Recall is a tiny persistent memory store for AI agents. Your agent saves facts, decisions and context under keys, then recalls them in a later session — surviving context resets. One URL. No SDK. No LLM. Free.

No signup. Pick any secret string of 16+ characters — that's your private memory namespace. Paste it into your MCP client and it's created on first use:

{
  "mcpServers": {
    "recall": { "url": "https://recall.notdown-app.workers.dev/mcp/" }
  }
}

Prefer a random key generated for you? Click below:

Your key (save it — it's the only copy):

Add to any MCP client (Claude Desktop, Cursor, etc.) as a remote/streamable-HTTP server:

Or use plain HTTP from any agent:

Try it right here. Save a memory, then recall it — this calls the real API live from your browser (an isolated demo namespace, not counted in stats).

Key Value

Tip: reload the page and hit “Recall” — your memory survives, because it's stored server-side under your demo key. That's exactly what your agent gets across sessions.

Why Recall

Zero friction. One HTTP endpoint. No SDK to install, no vendor lock-in, no config file wrangling.
Deterministic. Your memories are stored and returned verbatim — no model re-summarising or hallucinating them.
Works two ways. Native MCP tools for MCP-aware agents, and a plain REST API for everything else.
Private by key. Each key is an isolated namespace. Nobody else can read yours.

HTTP API

# save a memory
curl -X POST https://recall.notdown-app.workers.dev/api/save \
  -H "Authorization: Bearer $KEY" -H "content-type: application/json" \
  -d '{"key":"user_pref_theme","value":"dark","tags":["prefs"]}'

# recall it later
curl "https://recall.notdown-app.workers.dev/api/recall?key=user_pref_theme" -H "Authorization: Bearer $KEY"

# search across your memories
curl "https://recall.notdown-app.workers.dev/api/search?q=theme" -H "Authorization: Bearer $KEY"

# list keys / forget one
curl "https://recall.notdown-app.workers.dev/api/list" -H "Authorization: Bearer $KEY"
curl -X DELETE "https://recall.notdown-app.workers.dev/api/forget?key=user_pref_theme" -H "Authorization: Bearer $KEY"

MCP endpoint

Streamable-HTTP JSON-RPC at https://recall.notdown-app.workers.dev/mcp. Authenticate with your key as a Bearer token, or embed it in the path: https://recall.notdown-app.workers.dev/mcp/<your-key>. Tools: memory_save, memory_recall, memory_search, memory_list, memory_forget.

Don't want to trust my server? Self-host it.

Recall is one open Cloudflare Worker — no build tooling, no dependencies. Run an identical copy on your own account so your agent's memories never leave your infrastructure:

# grab the exact source running here + a starter config
curl -o index.js     https://recall.notdown-app.workers.dev/recall.worker.js
curl -o wrangler.toml https://recall.notdown-app.workers.dev/wrangler.toml

# create your own D1 database, paste its id into wrangler.toml, deploy
npx wrangler d1 create recall
npx wrangler deploy

Same MCP + REST API, your data, your account. That's the zero-trust option — most memory platforms can't be self-hosted in two commands.

Prefer to use this server but stay lock-in-free? Pull everything back anytime as JSON — curl -H "Authorization: Bearer $KEY" https://recall.notdown-app.workers.dev/api/export — or delete any key with /api/forget. Your data is always yours.