Set up WhiteMagic.

Find the WhiteMagic MCP server (whitemagic.dev; official MCP registry id io.github.lbailey94/whitemagic-mcp).
Install it with the one-line installer:
curl -fsSL "https://www.whitemagic.dev/install.sh?ref=ask-ai" | sh
Then run `wm connect --write` to wire my clients and `wm grimoire` to verify.
Report the readiness output and a test memory.

Who can do this

• ·Works in most clients that can run shell commands — Claude Code, Codex CLI, opencode, and similar terminal-capable agents can carry the prompt out end to end.
• ·Clients that can browse the official MCP registry can search for io.github.lbailey94/whitemagic-mcp and add it directly, with no shell step.
• ·Terminal-native path, one client at a time: wm setup <client> (claude · cursor · windsurf · codex · opencode) shows the change first; add --write to apply it with a timestamped backup.
• ·No terminal at all? Paste the matching config by hand from the client tabs below — the generic mcpServers entry works in most clients.
• ·Prefer not to install a binary? The npm launcher npx whitemagic-mcp serve runs the same server.

The per-client tabs below remain the manual fallback; where a client ships its own add command, that one-liner also works (Claude Code: claude mcp add whitemagic -- wm serve).

1. 01

   Install

   curl -fsSL "https://www.whitemagic.dev/install.sh?ref=guide-step" | sh

   Linux x86-64 is install-gated; macOS and Windows binaries are published, not yet install-gated. No account, no admin rights — the binary lands in ~/.local/bin.

   install details and downloads ↓

2. 02

   Verify readiness

   wm grimoire

   Checks the host, verifies the substrate and the release, configures detected agents (add --write to apply), calibrates memory, and demonstrates restart continuity. It reports five separate readiness facts instead of one green badge; --json for machines.

3. 03

   Wire your clients

   wm connect --write

   wm connect alone is a dry run that lists every detected client and the exact change; --write applies them (timestamped backups first) and finishes with an end-to-end connection test — initialize + tools/list against a real server.

4. 04

   Load your data

   wm ingest --source <folder> --dry-run

   Walk a folder of notes or transcripts into a local galaxy. Redaction, skip policy, and the resume ledger are in Load your data below.

   load your data ↓

5. 05

   Start a session, then resume

   wm session start --title "first run"

   Record decisions as you work and recall them in the next session — over MCP (session.start · session.record · session.continuity) or from the terminal (wm session start · record · continuity). wm quickstart demonstrates a full stop/start on an isolated store; wm selftest runs the end-to-end invariant check on a throwaway one.

keep it healthy

• wm status— Human-facing health summary: store, counts, index, backup, and update state.
• wm stats— Resource usage and brain-wave state; --week shows the last seven daily rollups.
• wm report— Writes a sanitized local support bundle (report.json + README.txt). Read-only; nothing is transmitted.
• wm backup— Copies the full store (LMDB + indexes + all JSON state) into a timestamped directory with a SHA256SUMS manifest. Stop the server first; restore with wm restore --backup <dir>.
• wm update check— Checks for a newer signed release — notify-only, no installation.

The store lives at ~/.local/share/whitemagic by default; --store <path> or a per-project client config points a server at another one. One store per project, and WM_PROJECT=<name> names the project in the MCP handshake, so an agent can confirm its scope before acting.

Uninstall: remove the wm binary and the store directory. That removes only those locations — backups, exports, replicas, and other project stores remain, and deletion is not secure erasure. Inventory the copies first.

claude mcp add whitemagic -- wm serve

{
  "mcpServers": {
    "whitemagic": {
      "command": "wm",
      "args": ["serve"]
    }
  }
}

[mcp_servers.whitemagic]
command = "wm"
args = ["serve"]

{
  "mcpServers": {
    "whitemagic": {
      "command": "wm",
      "args": ["serve"]
    }
  }
}

{
  "mcpServers": {
    "whitemagic": {
      "command": "wm",
      "args": ["serve"]
    }
  }
}

{
  "servers": {
    "whitemagic": {
      "type": "stdio",
      "command": "wm",
      "args": ["serve"]
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whitemagic": {
      "type": "local",
      "command": ["wm", "serve"],
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "whitemagic": {
      "command": "wm",
      "args": ["serve"]
    }
  }
}

{
  "mcpServers": {
    "whitemagic": {
      "command": "wm",
      "args": ["serve"]
    }
  }
}

Run once, then ask your client what it remembers.