Install Ricord — pick your client

All four guides share the same three commands:

bun add -g ricord
ricord login
ricord install   # auto-detects every MCP client on your machine

ricord install writes the right config block in the right place for every client it finds. The per-client guides exist for the verification steps, the smoke tests, and the gotchas — particularly where PATH inheritance, sandbox profiles, or per-OS config paths differ.

Per-client guides

Don't see your client?

Any client that speaks the Model Context Protocol can connect to Ricord. The MCP server config looks the same everywhere — a command, an args array, optional env. The block to add is:

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

Or the TOML equivalent for clients that use TOML (Codex): [mcp_servers.ricord] with command = "ricord" and args = ["mcp"]. If your client supports MCP but isn't auto-detected by ricord install, drop a note in the docs and we'll add it.

Cross-client memory

The same ricord install wires every MCP client on your machine to the same memory backend. Switch between Claude Desktop and Cursor mid-debugging, or jump from a Codex session in the terminal to a Composer chat in Cursor — the wiki view and recall are consistent across all of them.

Memory is scoped per project automatically, so the four side-projects you work on in different tabs don't leak into each other.