Who it is forA developer setting up the same agent memory on a new laptop or a CI image, who cannot answer installer questions.
The problemInteractive installers stall in scripts, and wiring an MCP server into Claude Code, Cursor and Codex by hand is three different config files.
The outcomeCausal Memory is built, registered with every detected client, and its tools show up after an agent restart.
What you need first
- Rust toolchain, or pip for the prebuilt package
- An MCP client such as Claude Code
Steps
- Run
git clone https://github.com/JingxuanC/causal-memory.gitandcd causal-memory - Run
./install.sh --yesto accept all defaults (skill, server and MCP registration across detected clients) - Restart Claude Code, Cursor or your other agent so it reloads its MCP list
- Ask the agent to list its MCP tools and confirm the Causal Memory tools are there
- To undo it later, run
./install.sh --uninstall
Prompt for your agent
Install JingxuanC/causal-memory on <machine> with `./install.sh --yes`, then restart and list the MCP tools you can see. Report which clients were registered and confirm the database path it uses.
Caveat. The installer builds with cargo, so a Rust toolchain must be present; without one, `pip install causal-memory` gives you the same server binary to register by hand.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for JingxuanC/causal-memory and "Install the memory server non-interactively"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer