memo MCP server

by jagoff·io.github.jagoff/memo·v4.16.0

No reviews yet

Memory for AI agents — MLX (Apple Silicon) or CPU (Linux), sqlite-vec + BM25, zero cloud.

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

Growing

19 stars429 downloads/wk

Reviews

Write one

Nobody has reviewed memo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

memo tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

read_only_hint
Read a tool's read-only hint across both MCP SDK spellings.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 medium

Code scan566 source files scanned20/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

mediumeval / new Function usedexec.eval

mlx_memo-4.16.0/src/memo/cli_dream_passes.py: … -> dict: """Nightly retrieval-only eval (vec mode, no reranker — the same fast pa…

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

What the publisher says

From the memo repository's README, as published. We do not edit it. Read it on GitHub

memo

Your coding agent starts every session with amnesia. memo fixes that — 100% on your own machine.

Persistent, searchable memory for Claude Code, Codex, Cursor, Cline, Devin, and OpenCode. No cloud, no API keys, no Ollama, no vector DB to run. And it spends fewer tokens, not more.

Install

curl -fsSL https://raw.githubusercontent.com/jagoff/memo/v4.16.0/install.sh | bash

Prefer a package manager? uv tool install mlx-memo · pipx install mlx-memo · brew tap jagoff/memo && brew install mlx-memo

Then:

memo doctor                                   # self-check
memo save 'we use Postgres, not Mongo'        # save a decision
memo search 'what database did we pick?'      # search by meaning

That's it. Your agents pick it up over MCP automatically — the installer wires every client it finds.

Installing on another Mac or handing setup to an agent?

New Mac:

curl -fsSL https://raw.githubusercontent.com/jagoff/memo/v4.16.0/install.sh | bash
memo sync bootstrap git@github.com:yourname/memo-sync.git

Agent-managed setup:

curl -fsSL https://raw.githubusercontent.com/jagoff/memo/v4.16.0/install.sh | bash
memo doctor --strict-runtime

On Linux or just want to look around first?

docker run --rm ghcr.io/jagoff/memo:latest memo doctor

Why this saves you money

Most memory servers add context. memo is built to remove it.

The default MCP surface is 43 tools, not 165 — 74% fewer tools, and about 68% less schema context: 43 tools / ~9.7k schema tokens versus 165 tools / ~30.6k tokens on the full surface — overhead paid every session, in every client.

Ambient recall injects one relevant memory before the model answers. The bundled Claude Code hook caps that injection at ~160 tokens. memo roi reports the real grounding and re-ask counts — the estimated-savings figure it used to print was removed in 4.14.0, because multiplying those counts by hardcoded constants was a savings claim memo could not support. For measured savings, memo tokens reads the provider's own usage counters through the context-compression proxy.

memo roi       # value from grounded recalls and avoided re-asks
memo tokens    # usage-savings ledger

Three things nothing else does

🕰️ Time-machine — query your knowledge as it was

memo as-of ask "what was the deploy strategy?" --date 2026-02-01
memo diff --from 2026-01-01 --to 2026-03-01

Full historical reconstruction by reverse-replaying history.db. Useful when you need to know why past-you made a call, not just what past-you decided.

⚡ Contradiction radar — memory that notices when you change your mind

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

claude mcp add memo -- uvx mlx-memo

Add to Cursor

memo: common questions

Is memo MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the memo safety report
How do I install memo?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does memo need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is memo maintained?: The last commit was in the last day (2026-09-20). The latest release is v4.16.0.
What can I use instead of memo?: Servers from other publishers that do the same job: KEPTA — Agent Memory MCP server, Remem MCP server and Myc MCP server. Compare all memo alternatives.

Alternatives to memo

Same job from other publishers: the closest match first, then the best rated.

All memo alternatives →

KEPTA — Agent Memory
Local memory for AI agents. One SQLite file on your machine — no cloud, no account.
not reviewed
Growing
A
Remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.
not reviewed
Established
B
Myc
Task queue, decisions and memory for coding agents. Local SQLite, no network. Requires Bun.
not reviewed
Growing
C
skillmem
Skill memory for coding agents: learn, recall, reinforce, decay. Local SQLite, no API key.
not reviewed
Growing
A
Memory Arbiter
Local SQLite MCP memory: evidence-based recall, advisory conflict notices, authorized governance.
not reviewed
Growing
A

memo vs KEPTA — Agent Memory memo vs Remem memo vs Myc