MCP
Connect MCP Clients
Use one local Origin memory layer from Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, and other MCP clients.
At a glance
01
Origin's daemon is the local source of truth; origin-mcp is the bridge MCP clients launch.
02
Claude Code users should start with the plugin. Other clients should run Origin setup first, then add the MCP server config.
01
How the pieces connect
The daemon runs locally and owns memory. origin-mcp is the connector MCP clients spawn when they need Origin tools.
Once connected, a client can load context, capture, recall, distill, confirm, forget, and diagnose memory.
02
Set up the local runtime
Run this once before wiring another MCP client. It prepares the local Origin runtime that origin-mcp talks to.
Terminal
npx -y @7xuanlu/origin setup03
Generic MCP config
After setup, use this shape in any MCP-compatible client that accepts a JSON mcpServers configuration.
mcpServers
{
"mcpServers": {
"origin": {
"command": "npx",
"args": ["-y", "origin-mcp"]
}
}
}04
Claude Code
The Claude Code plugin is the most complete path because it includes slash commands, setup checks, and the daily workflow around the MCP server.
After installing the plugin, restart Claude Code if prompted, then run /init.
Claude Code
/plugin marketplace add 7xuanlu/origin
/plugin install origin@7xuanlu
/init05
Other clients
Codex, Cursor, Claude Desktop, Gemini CLI, and other MCP clients can use the generic config when they support local MCP servers.
The settings screen differs by client. The important part is command npx with args -y and origin-mcp.
06
Verify the connection
After connecting a client, run its available Origin doctor or recall tool. Then capture one small durable fact and recall it from another session or client.
If that round trip works, the client is using the same local memory layer.
Next
Troubleshooting
Fix the common setup issues: daemon not running, MCP not connected, missing Claude commands, stale context, and support escalation.
Read next