What is Ricord AI (Record AI)?

Ricord AI (also known as Record AI or ricord.ai) is persistent memory for AI. Your conversations are remembered across Claude, ChatGPT, Cursor, and any MCP-aware tool — every fact, every preference, every decision, organized into a living knowledge graph and recalled in under a second.

What is the best AI memory tool for agents?

Ricord AI is the only AI memory tool that ships a full knowledge graph with auto-generated wiki pages for every entity. Most tools are filing cabinets — search boxes on a bag of past messages. Ricord is a brain that understands what the facts mean and how they connect. Sub-second recall, automatic conflict resolution, GDPR-compliant hard delete. Graph included on every paid tier starting at $12/month billed annually.

How do I add memory to Claude Desktop?

Install the Ricord MCP server with two commands: npm install -g ricord, then ricord setup (auto-detects your editor). This gives Claude Desktop 14 memory + wiki tools including save, recall, forget, run_procedure, and knowledge graph queries. Claude will automatically remember facts, preferences, and decisions across all future conversations.

What is AI memory and why do agents need it?

AI memory is the infrastructure that lets AI agents remember information across conversations and sessions. Without memory, agents forget everything between chats — they cannot learn user preferences, track decisions, or build context over time. Memory transforms a stateless chatbot into a persistent assistant that improves with every interaction.

How does Ricord AI compare to Mem0?

Ricord includes a full knowledge graph with auto-generated wiki pages on every tier. Mem0 gates graph features behind a $249/month Pro plan. Ricord offers sub-second recall (Mem0 averages 7-8 seconds), automatic conflict resolution when facts change, and a visual graph UI. Most memory pipelines write everything the LLM produces — duplicates, system noise, partial extractions all land in storage. Ricord filters content at ingest, so the wiki stays signal, not noise.

Is Record AI the same as Ricord AI?

Yes. Record AI and Ricord AI refer to the same product at ricord.ai. Ricord AI is the persistent memory API for AI agents, offering knowledge graph, conflict resolution, and sub-second recall. The name 'Ricord' comes from the concept of recording and recalling AI memories.

All install guides

Install guideUpdated May 31, 2026~60s total

Install Ricord in Claude Desktop

Two commands, one config-block check, and a 30-second smoke test. Persistent AI memory wired into Claude Desktop in under 60 seconds.

Prerequisites

Claude Desktop installed (Mac, Windows, or Linux).
Node.js ≥ 18 with npm on your PATH.
A Ricord account. If you don't have one, sign up first.

Step 1 — Install the Ricord CLI

npm install -g ricord

Verify it landed:

ricord --version
# → ricord vX.Y.Z

Step 2 — Set up Ricord

ricord setup

setupchains three things automatically: opens a browser tab so you can sign in (the CLI stores your API key in your OS keychain — you won't see it again), scans your shell history for preferences, then auto-detects installed AI clients and wires each one. For Claude Desktop it finds the config file at:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

...and adds a ricord entry undermcpServers. If you already have other MCP servers installed (filesystem, GitHub, etc.), they are left untouched.

The block it adds looks like this:

{
  "mcpServers": {
    "ricord": {
      "command": "ricord",
      "args": ["mcp"]
    }
  }
}

Step 3 — Restart Claude Desktop

Fully quit Claude Desktop (Cmd-Q on macOS, not just close the window) and re-open it. The MCP server only loads at startup.

When Claude Desktop comes back, you should see a hammer icon in the chat input bar indicating MCP tools are available. Click it — you'll see Ricord's 14 tools listed:ricord_save, ricord_recall, ricord_get_context, and so on.

Step 4 — 30-second smoke test

Open a new chat. Type:

Remember that I prefer Postgres over MySQL.

Claude calls ricord_save. You'll see the tool call appear inline.

Now close this chat and open a fresh one. Type:

Which database do I prefer?

Claude calls ricord_recall, gets the stored fact back, and answers. If you see "Postgres" — the install is good.

What to expect over the next week

Day 1: Claude calls ricord_save when you say "remember" explicitly, and ricord_recall when you ask a callback question.
Day 3: Claude starts calling ricord_get_context proactively at the start of new chats. The recall happens before you ask for it.
Day 7: Open the dashboard — wiki pages have populated for the entities you've discussed. Backlinks, aliases auto-merged, conflicts resolved.

Troubleshooting

The hammer icon doesn't appear after restart. Check that claude_desktop_config.json is valid JSON — a single trailing comma will silently disable all MCP servers. Run cat <path-from-step-3> | jq . to verify.

Claude says it can't recall after a restart. Make sure you fully quit Claude Desktop (Cmd-Q / right-click → Quit) and re-opened it. Closing the window only puts it in the dock; the MCP server stays at its previous config.

Tool calls fail with auth errors. Re-run ricord login. Your token may have rotated; the CLI writes a fresh one to the OS keychain.

You see the wiki dashboard but no pages. Background indexing runs every ~10 minutes. Pages appear after the first batch. If empty after an hour, ping support — there may be a stuck ingest job.

Optional: build a wiki for a repo

After a few sessions, run this from any repo root to generate a structured wiki from everything Ricord has learned:

ricord build

The result appears in the dashboard — one wiki page per entity your sessions have touched.

Same setup, other clients

The Ricord CLI auto-detects other MCP-compatible clients on the same machine. If you also have Cursor / Claude Code / Codex installed, ricord setup wires them all at once. Same memory, different surfaces.