Install Prime in your tools

AllSource Prime provides durable memory over the Model Context Protocol. It works with any MCP-compliant client — the same hosted memory across every tool your agents touch. Pick yours below for a copy-paste setup.

Hosted memory

Mint an API key and Prime syncs to your AllSource tenant. The same key works across every client — watch nodes appear live in the dashboard.

Mint an API key

Local-only

No account needed. Run cargo install allsource-prime and keep memory on disk at ~/.prime/memory.

MCP setup docs

Two ways to reach Prime. MCP clients (the tools below) connect to the local allsource-prime stdio binary and sync to your tenant with --sync-to. For programmatic access, the same hosted memory is also a REST API behind the gateway at api.all-source.xyz/api/v1/prime — use an AllSource SDK for graph, vector, and recall calls. A hosted MCP-over-HTTP endpoint (connect a client with no local binary) is on the roadmap.

Choose your client

Claude Code

Wire Prime into Claude Code with one `claude mcp add` command — no config file to edit.

Claude Desktop

The original Prime surface — paste one JSON block, or double-click the .dxt bundle for a no-terminal install.

Cursor

Cursor reads stdio MCP servers from the same mcpServers shape as Claude Desktop.

Windsurf

Windsurf's Cascade reads MCP servers from an mcp_config.json with the standard mcpServers envelope.

VS Code

VS Code's built-in MCP support (Copilot agent mode) loads stdio servers from a workspace .vscode/mcp.json.

ChatGPT

Use Prime from ChatGPT desktop via its MCP connector — the same local stdio binary.

Codex

OpenAI's Codex CLI reads MCP servers from ~/.codex/config.toml under an [mcp_servers] table.

OpenCode

OpenCode uses its own envelope: a top-level `mcp` key, `type: "local"`, and command-as-array.

Using a client that isn't listed? Any MCP-compliant tool works — point it at the allsource-prime stdio binary. See the MCP setup docs for the generic config shape.