Main

Deploy Recall like infrastructure: decide whether memory data lives in your own Redis/Valkey or a managed instance, then wire the MCP command into your agent client config. For teams, treat memory as sensitive data and follow the README guidance on access control and TLS.

When onboarding, start with a small memory schema (directives/decisions/requirements) and only then expand to more granular memory types.

README excerpt (verbatim)

Recall 🧠

Persistent cross-session memory for Claude and other AI agents. Survives context limits, session restarts, and compaction.

Store decisions, patterns, and knowledge once — retrieve them automatically across every future conversation. No more repeating yourself. No more losing critical context when the window fills up.

Cloud vs. Self-Hosted

Recall comes in two flavours. Choose the one that fits your situation:

☁️ recallmcp.com — Managed SaaS (Recommended for most users)

Zero infrastructure. Sign up, get an API key, add one config block, done.

{
  "mcpServers": {
    "recall": {
      "url": "https://recallmcp.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

→ Get started at recallmcp.com

🖥️ This Repository — Self-Hosted (Redis or Valkey)

Run Recall entirely on your own infrastructure. Your data never leaves your servers.

Best for: developers who need full control, on-premise requirements, or who already run Redis infrastructure.

⚠️ Security & Privacy Disclaimer

IMPORTANT: READ BEFORE USE

Recall stores conversation memories in either Redis or Valkey, which may contain sensitive information including:

• Code snippets, API keys, credentials, and secrets discussed in conversations

FAQ

Q: Do I need Redis? A: No for managed mode—README says no Redis required for the cloud service; self-host uses Redis/Valkey.

Q: Is there a fast start path? A: README claims you can be up in ~2 minutes with one config block for the managed service.

Q: What’s the biggest risk? A: Memory can contain sensitive data; follow README security guidance for Redis/Valkey (auth, TLS, network controls).