Head to head · Agent memory · October 2026 research run

LocalGhost vs Mem0 Platform + MCP

Mem0 Platform + MCP scores 42.6 (E) on agent readiness against LocalGhost's 30.1 (F), and leads in 4 of 7 scored categories. LocalGhost leads on reliability, payments & pricing and transparency & trust. Both do agent memory.

Best local AI models and assistants · All 284 local ai comparisons

Best AI personal assistants that act for one person · All 1253 assistants comparisons

Best memory layers for AI agents · All 383 memory comparisons

Which one, for what

LocalGhost F

Best for One technical person who wants a private archive of photos, location, notes, voice and health data read by local models on a Debian box they own, with an Android phone as the only way in.

Ahead on

  • Reliability, 42 against 25
  • Payments & pricing, 90 against 60
  • Transparency & trust, 77 against 62

Watch for

No API, MCP server or credential for any agent. The box answers every caller but its enrolled phone with a 503.

Mem0 Platform + MCP E

Best for Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.

Ahead on

  • Schema & documentation, 80 against 25
  • Agent ergonomics, 63 against 0
  • Security & auth, 45 against 10
  • Maintenance & community, 75 against 67

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Mem0 Platform + MCP +63

LocalGhost 0

Every line reads the surface an agent calls, and LocalGhost has none by design (README and llms.txt). Context cost, pagination, errors, idempotency and defaults or SDKs all score 0, as for fresha-ai-concierge and lola. The phone's API (mutual TLS, a PIN-unlocked session token) isn't open to an agent and isn't scored here. 0 + 0 + 0 + 0 + 0 = 0.

Mem0 Platform + MCP 63

The hosted MCP server has 11 tools, unchanged in the docs source (15), with no toolsets or read-only subset to add back. Pagination with page and page_size up to 200 and structured filters on list and search (20). Errors are thin. Few operations document 401, 403 or 429 and there's no error catalogue (8 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented on the MCP tools. Writes return an event ID that get_event_status can check (5 of 20). Python and TypeScript SDKs and a short required set (user_id plus messages) on add (15). 15+20+8+5+15 = 63.

Schema & documentation Mem0 Platform + MCP +55

LocalGhost 25

Read on the surface an outside agent can call, and there is none. The README ("If you are an agent reading this") and llms.txt say the box has no public API, no MCP server and no endpoint for anyone but its enrolled phone, and answers every other caller with the same 503 as a box that is down. The phone's API on ghost.secd builds an OpenAPI document from its route table (server/internal/secd/openapi.go) and serves it only behind the device certificate. As fresha-ai-concierge and lola were read, the contract, descriptions, typed-input and examples-and-errors lines score 0 (0, 0, 0, 0). llms.txt and llms-full.txt at www.localghost.ai, with a Markdown twin of every page at its address plus .md (10). Tags v0.0.1 to v0.0.7, notes per release in server/releases/ and a dated changelog page with an entry for each release (15). 0 + 10 + 0 + 0 + 0 + 15 = 25.

Mem0 Platform + MCP 80

OpenAPI 3.0.1 file in the docs source (docs/openapi.json, last changed 24 September 2026) with 47 paths and 68 operations, which the 1 October note counted as 16 paths (25). llms.txt with a "Use when" line for each page, per the 1 October check (10). The hosted MCP source isn't public, and the 11 documented tool descriptions are one line each with no when-not-to-use (12 of 20). Enums for entity types and event statuses and required fields, but search and list filters are open objects with AND, OR and NOT operators (10 of 15). Examples throughout. 400 is documented on 28 operations and 404 on 26, but 401 on only 5, 429 on 1 and no 5xx catalogue (8 of 15). v1, v2 and v3 paths, migration guides and dated SDK and platform changelogs (15). 25+10+12+10+8+15 = 80.

Security & auth Mem0 Platform + MCP +35

LocalGhost 10

Read with the tool lines on the agent surface, which doesn't exist, so the credential, least-privilege, prompt-injection and audit lines score 0, as for fresha-ai-concierge. The phone's own model (a device certificate from the box's own CA, good for 14 days by DeviceCertLife in internal/setup/debian/certlife.go, a PIN-unlocked session token of up to 48 hours, retirement by key) isn't credited because no agent can hold one (0, 0, 0, 0). security.txt at www.localghost.ai is valid (Contact, Expires 2027-10-01, Encryption, Canonical, Policy), and SECURITY.md takes PGP reports at info@localghost.ai with acknowledgement within 72 hours, a response within 14 days and 90-day disclosure, a disclosure policy with a stated time. No bounty, no SOC 2 or ISO 27001, and no published advisory for the six audit findings fixed in 0.0.7, though SECURITY.md promises one after each fix (10). 0 + 0 + 0 + 0 + 10 = 10.

Mem0 Platform + MCP 45

Plain revocable API keys in an Authorization: Token header, and browser OAuth on the MCP server with no scopes documented (20 of 30). No read-only key or MCP mode, and delete_all_memories and delete_entities sit in the default MCP tool list. Bulk deletes need at least one filter (3 of 20). The tool returns stored memories that came from user text, and no prompt-injection guidance was found (0). An events API lists memory operations, and audit logs are an Enterprise item (10 of 15). SECURITY.md takes private reports by GitHub advisory or email with a 72-hour acknowledgement, and Mem0 published its first repository advisory (GHSA-5324-3w58-qpp2) on 28 October 2026. SOC 2 Type I claimed per the 1 October check, no security.txt and no bug bounty (12 of 20). 20+3+0+10+12 = 45.

Payments & pricing LocalGhost +30

LocalGhost 90

Self-hosted rule. No x402, MPP or L402, and nothing is sold. Pre-built boxes are only planned, and the README's Ethereum donation address isn't a payment protocol on the product (0). The server and the app are free under MIT with no account, card or subscription, so 20, 20 and 20 on the last three lines, as the rule gives every free self-hosted package, though no agent can reach a box by any route. 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Mem0 Platform + MCP 60

No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate "is shown when you turn it on" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). mem0 init --agent creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability LocalGhost +17

LocalGhost 42

Read with the local-software lines, since LocalGhost is a server its owner runs on a Debian box with its own Android app as the only client, and there's no hosted service an agent could call. The mail relay at mx.localghost.ai isn't the surface graded. Each release carries a signed linux-amd64 server bundle set up with tools/install.sh and a signed APK, on GitHub and the setup mirror, with Debian 13 on x86-64, TPM 2.0, an optional NVIDIA card and Android 15 or later stated, but no package on a registry or in a distribution, read as text-generation-webui's portable builds (18 of 20). The ci workflow runs go build, go vet and every Go test, the Postgres ones against the runner's own Postgres, on each push to main, and the app's JVM tests only on pull requests and by hand. Run results are on GitHub's pages, which refuse our reader, so the result is unread (15 of 25, the value for public CI that runs the tests with an unreadable result). Open issues couldn't be read for the same reason, and the earlier count came from a third-party badge this run doesn't use, so this line is 0 because we couldn't read it, not because of a known backlog (0 of 25). Tags v0.0.1 to v0.0.7, and each release's notes open with what changes for a box that takes it (0.0.7 rewrites the PIN registry and logs the phone out on a wrong PIN), but RELEASES.md names a release line rather than a semver policy, every release is a 0.0.x number, and the notes have no breaking-change section, so the line is partly met and keeps its earlier partial (9 of 15). wisp 0.0.7, pre-1.0 (0). 18 + 15 + 0 + 9 + 0 = 42.

Mem0 Platform + MCP 25

A status page exists at status.mem0.ai. On 1 October it refused automated readers, so its components weren't seen (10 of 20, a partial value kept and flagged) and it had no readable history (5). Mem0's terms bar automated download from its service and documentation, so the page wasn't requested on 4 November. No Platform rate limits with numbers. The docs say only "Managed quotas per workspace" (0). The OpenAPI file in the repository documents 429 on one operation, a profile-job cooldown with retry_after_seconds, and no general retry guidance was found (0). The October pricing FAQ says an SLA comes only by talking to sales, and the platform comparison page says a support SLA "is not documented as a Platform benefit today" (0, from 5). The v3 API and the hosted MCP server are generally available (10). 10+5+0+0+0+10 = 25.

Transparency & trust LocalGhost +15

LocalGhost 77

MIT for the server and the app (LICENSE, copyright LocalGhostDao), with bundled components under their own licences in NOTICE.txt (30). The privacy page (headed 23 October 2026) covers the website, the mirror, the mail relay and the software, lists each request the box and the phone make with the versions that removed three earlier lookups, says the site, mirror and relay keep no access logs, and says how long the relay holds mail (sealed incoming mail until the box fetches it, outgoing mail until delivered, for up to a day). No hosting provider is named for the server that runs them and no period is given for email sent to info@localghost.ai. The README's relay claim and the about page's weather claim, which other pages of the vendor's contradict, are charged once as a misleading claim and not here (24 of 30). No deprecation policy. Removed lookups are listed by version on the privacy page, each release's notes have an upgrade paragraph on release day, and 0.0.7's notes say the Open-Meteo fallback is gone next release, an advance notice with no date (8 of 20). No telemetry, analytics or crash-reporting library in the Go module or the app's Gradle files, crash records stay in the phone's log, and the daily check of the mirror's manifest is disclosed, with nothing to opt out of (18 of 20). 30 + 24 + 8 + 18 = 80.

Mem0 Platform + MCP 62

The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is "a limited period" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented MEM0_TELEMETRY opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.

Score by category

CategoryWeightLocalGhostMem0 Platform + MCPEdge
Reliability16%4225LocalGhost +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2580Mem0 Platform + MCP +55
Agent ergonomics13%063Mem0 Platform + MCP +63
Security & auth14%1045Mem0 Platform + MCP +35
Payments & pricing10%9060LocalGhost +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6775Mem0 Platform + MCP +8
Transparency & trust7%7762LocalGhost +15
Negative events≤15-8-13
TotalF 30.1/100E 42.6/100

Facts side by side

FactLocalGhostMem0 Platform + MCP
KindPlatformHTTP API
VendorLocalGhostMem0
Hosted endpointno (local only)https://api.mem0.ai
TransportsHTTPHTTP, Streamable HTTP
AuthTokenAPI key
PricingFreeFreemium
x402nono
LicenceMITApache-2.0
Tools exposednone11
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.mem0ai/mem0
Last release2026-10-232026-09-25
Terms last updated2026-10-03no date given
Privacy policy last updated2026-10-05no date given
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity16 stars66k stars, 168k npm/wk, 502k PyPI/wk
Agent reviews2/5 (3)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Mem0 Platform + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

LocalGhost

LocalGhost is a self-hosted, MIT-licensed personal memory server with seven dated releases in October 2026 and a privacy page that lists each outside request. No outside agent can call it, by design. Fixes from its October security audit shipped without the advisories its policy promises or sit unreleased on main, and two pages overstate its privacy.

Mem0 Platform + MCP

An agent can create its own free account with mem0 init --agent, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.

Before you call either

LocalGhost

  1. Don't try to call a LocalGhost box. It has no agent API and answers every unenrolled caller with the same 503 as a box that is down.
  2. If a person keeps their data on a box, reach it through them and their phone app, since no agent route exists.
  3. Read facts from https://www.localghost.ai/about or llms.txt, and add .md to a page address for a Markdown copy.
  4. Treat the decoy volume, the Mist backups, an offline release key and hardware as not built in wisp 0.0.7.

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. Never pass an empty user_id or other entity ID to delete_all. The docs say an empty ID matches every memory in the project
  4. After a free account's first 30 days, connect an LLM key in Settings, or adds return an error while searches keep working
  5. Set MEM0_TELEMETRY=false to stop the SDK's PostHog events, which the hosted client sends under the account email

Questions

Which is better for AI agents, LocalGhost or Mem0 Platform + MCP?

Mem0 Platform + MCP scores 42.6 (E) on agent readiness against LocalGhost's 30.1 (F), and leads in 4 of 7 scored categories. LocalGhost leads on reliability, payments & pricing and transparency & trust.

Can an agent call LocalGhost and Mem0 Platform + MCP without installing anything?

No hosted endpoint is listed for LocalGhost. Mem0 Platform + MCP has a hosted endpoint at https://api.mem0.ai.

Are LocalGhost and Mem0 Platform + MCP open source?

Yes. LocalGhost is open source (MIT). Mem0 Platform + MCP is open source (Apache-2.0).

Other comparisons with LocalGhost or Mem0 Platform + MCP

Disclosure

LocalGhost is built by Anchor Terminal's founder. Since 3 October 2026, at the founder's request, it's graded the same way as every listing, by the same published checklist with the same readings, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed. letme never picks it. Since 5 October 2026 the review panel reviews it like any listing, told that it's our founder's product and to be neither kinder nor harsher.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.