AllSource Prime with Claude Desktop
The original Prime surface — paste one JSON block, or double-click the .dxt bundle for a no-terminal install.
Prime runs as a local allsource-prime binary over stdio in Claude Desktop. 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:
{
"mcpServers": {
"prime": {
"command": "allsource-prime",
"args": [
"--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.
{
"mcpServers": {
"prime": {
"command": "allsource-prime",
"args": [
"--data-dir",
"~/.prime/memory",
"--auto-inject"
]
}
}
}Notes
- Easiest path: download the `.dxt` bundle from the latest GitHub release and double-click it — Claude Desktop prompts for your API key and writes the config for you.
- Fully quit and relaunch Claude Desktop (not just close the window) after editing the config.
- On macOS, Claude Desktop may need Full Disk Access for data dirs outside your home folder.
After install
- Restart Claude Desktop 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.