LocalGhost vs Memory (MCP reference server)

LocalGhost

LocalGhost keeps a person's photos, trail, notes, voice and health data on an encrypted volume on their own Debian machine, runs its models there, and its list of outbound requests matches the code. It's pre-1.0 at wisp 0.0.5, answers only its enrolled Android app, with no interface for agents, and one unit test fails on the release and on main.

Memory (MCP reference server)

Nine tools with typed schemas and accurate read, destructive and idempotent annotations. No pagination or limits. read_graph returns everything and search_nodes every match.

LocalGhost

1. Don't look for an API or MCP server. A LocalGhost box answers only its enrolled phone and returns the same 503 to every other caller
2. Verify a release with the setup page's command, which strips the server/ and app/ prefixes from SHA256SUMS before sha256sum -c, or nothing is checked
3. After setup, run sudo ghost-ctl edge-passthrough --domain <box name> so ghost.secd checks the device certificate itself
4. Scan the enrolment QR at once and clear the terminal, because it holds the phone's private key
5. Install from the v0.0.5 release, not main, which carries unreleased 0.0.6 work

Memory (MCP reference server)

1. Set MEMORY_FILE_PATH to an absolute path. The default sits inside the npx cache
2. Use search_nodes or open_nodes instead of read_graph once the graph has more than a few hundred entities
3. Make memory writes one at a time. Parallel calls in one turn can overwrite each other in 2026.8.31
4. Create both entities before create_relations. A missing endpoint fails the whole batch
5. Keep observations short and factual. They come back verbatim in every later read