LocalGhost vs Mem0 Platform + MCP

LocalGhost

The server and Android app are MIT-licensed, with no telemetry libraries found. There is no agent API, MCP server or SDK; unpaired callers receive HTTP 503.

Mem0 Platform + MCP

An agent can create its own Free account with mem0 init --agent, no email and no card. Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026.

LocalGhost

1. Don't call a LocalGhost box. Every request without the paired phone's certificate gets a 503 that looks like an outage
2. Reach a person's LocalGhost archive through the person and their phone. Nothing in wisp 0.0.3 opens it to an agent
3. Read a 503 from a box as no certificate, a retired phone, a locked box or a down daemon. The response never says which
4. Don't treat the README's list of what leaves the phone as complete. The app also calls Frankfurter, Wikipedia's summary API and Android's geocoder
5. Run ghost-cli ghost.<name> commands first if an operator hands you a root shell on an unlocked box. It lists command names only, takes key=value arguments and prints JSON

Mem0 Platform + MCP

1. Send the REST key as Authorization: Token <key>, and the MCP key as Bearer
2. Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
3. Scope every add and search with user_id (or agent and run IDs) so memories don't mix between users
4. Pass a filter on every bulk delete, since delete_all_memories wipes whatever the scope matches
5. On Hobby and Starter, count retrievals rather than adds. The retrieval quota is a tenth the size