AllSource Prime with Claude Code
Wire Prime into Claude Code with one `claude mcp add` command — no config file to edit.
Prime runs as a local allsource-prime binary over stdio in Claude Code. The same store serves every MCP client you wire it into — one source of truth, everywhere your agents work.
1. Install the binary
From crates.io. Builds standalone — no AllSource server required, just a Rust toolchain.
cargo install allsource-prime2. Hosted memory (recommended)
Mint an API key, then run Prime with --sync-to. Your memory persists to your AllSource tenant and shows up live in the dashboard — and the same key works from any other client you connect.
One click mints a Prime-scoped key. We don't show secrets twice — paste it into the config below.
Then paste this, swapping <YOUR_API_KEY> for the key you just minted:
claude mcp add prime allsource-prime \
--data-dir ~/.prime/memory \
--auto-inject \
--sync-to https://api.all-source.xyz \
--api-key <YOUR_API_KEY>3. Local-only alternative (no account)
Skip the account entirely. Drop the --sync-to / --api-key flags and memory stays on disk at ~/.prime/memory. Nothing leaves your machine.
claude mcp add prime allsource-prime \
--data-dir ~/.prime/memory \
--auto-injectOr let the agent do it
Claude Code can edit its own config. Paste this prompt and let it wire Prime up:
Install the AllSource Prime MCP server for me. Run `cargo install allsource-prime`, then `claude mcp add prime allsource-prime --data-dir ~/.prime/memory --auto-inject`. Confirm it registered with `claude mcp list`.Notes
- Run `claude mcp list` to confirm the `prime` server registered.
- The flags after `allsource-prime` are passed through to the binary, not to `claude`.
After install
- Restart Claude Code so it picks up the new MCP server.
- Verify by asking it: "List the MCP tools you have available." You should see
prime_add_node,prime_recall, and friends. - On the hosted path, watch nodes appear live at /dashboard/memory.