Setup
Claude Desktop MCP Memory Setup with Origin
Connect Claude Desktop to Origin's local memory daemon through MCP and verify the first memory loop.
Article packet
Workflows
Claude Desktop users adding local MCP memory
5 min read
01
Use the MCP-only setup path for Claude Desktop on supported local setups.
02
Origin's daemon remains local on your machine.
03
Verify with doctor, then capture and recall a harmless durable fact.
01
Quick answer
On macOS, install Origin and run ~/.origin/bin/origin mcp add claude-desktop to write the Claude Desktop MCP config. Restart Claude Desktop, then use Origin's doctor and capture/recall tools to verify the local daemon connection.
Origin gives Claude Desktop a local memory server while preserving the same daemon and artifacts used by coding clients. That makes desktop research or planning available to later coding sessions.
02
When this problem appears
Claude Desktop MCP users often add tools one by one, but memory only becomes useful when captures, retrieval, and maintenance all point at the same local store.
03
Connect Claude Desktop
Use the CLI-generated configuration first; use manual config only when a client needs raw JSON.
- Install the local runtime with the current setup path for your operating system.
- Run ~/.origin/bin/origin mcp add claude-desktop.
- Use ~/.origin/bin/origin mcp add claude-desktop --dry-run if you want to inspect the JSON before writing it.
- Restart Claude Desktop after MCP config changes.
- Use the Origin MCP doctor tool or the origin doctor CLI if tools fail to call the daemon.
- Recall a known capture before trusting the setup for real work.
Claude Desktop MCP setup
npx -y @7xuanlu/origin setup
~/.origin/bin/origin mcp add claude-desktop
~/.origin/bin/origin mcp add claude-desktop --dry-run04
What to check next
Do not expose the local daemon beyond loopback unless you are intentionally doing development or self-hosted networking work. Normal desktop setup should stay local.
Try the local memory loop
Install Origin, connect your AI client, and verify that capture, recall, and handoff work on your machine.
FAQ