AllSource Prime with VS Code

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

Connect VS Code to hosted Prime over HTTPS with nothing to install, or run the local allsource-prime binary over stdio. The same store serves every MCP client you wire it into — one source of truth, everywhere your agents work.

Hosted MCP URL — nothing to install (recommended)

Mint an API key, then point VS Code at the hosted endpoint. Memory lives in your AllSource tenant and shows up live in the dashboard.

Mint your API key

We don't show secrets twice — paste it into the config below.

Get API key

Then paste this, swapping <YOUR_API_KEY> for your key:

Paste into: .vscode/mcp.json

{
  "servers": {
    "prime": {
      "type": "http",
      "url": "https://api.all-source.xyz/api/v1/prime/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Prefer a local binary? The steps below run Prime on your machine instead.

1. Install the binary

From crates.io. Builds standalone — no AllSource server required, just a Rust toolchain.

cargo install allsource-prime

2. Hosted memory via the local binary

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.

Mint your API key

One click mints a Prime-scoped key. We don't show secrets twice — paste it into the config below.

Get API key

Then paste this, swapping <YOUR_API_KEY> for the key you just minted:

Paste into: .vscode/mcp.json

{
  "servers": {
    "prime": {
      "type": "stdio",
      "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.

Paste into: .vscode/mcp.json

{
  "servers": {
    "prime": {
      "type": "stdio",
      "command": "allsource-prime",
      "args": [
        "--data-dir",
        "~/.prime/memory",
        "--auto-inject"
      ]
    }
  }
}

Notes

VS Code uses a top-level `servers` key (with `type: "stdio"`), NOT the `mcpServers` key the desktop clients use.
Requires GitHub Copilot with MCP/agent mode enabled. After saving, click Start on the server in the .vscode/mcp.json gutter.

After install

Restart VS 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.

← Other integrations MCP setup docs