Offline persistent memory for AI coding agents — 37 tools, 80% fewer calls, no LLM
If you already use Toon Memory, the toon memory mcp server is the piece that lets your assistant work with it directly. Offline persistent memory for AI coding agents — 37 tools, 80% fewer calls, no LLM.
Ever had that feeling where your AI agent forgets everything from yesterday's session? You explain the same architecture decision for the third time, and it still suggests the approach you already rejected?
toon-memory on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
memory_remember — Save a decision, pattern, bug, knowledge, or warning (negative "do NOT do this" memory, recalled with a boost) — optional TTL, auto-tagmemory_recall — Search memory (use BEFORE reading files, filters expired TTL). mode: "graph" expands a relationship-aware subgraph for higher precision. budgetmemory_smart_recall — Unified recall: BM25 + graph + decay + quality in one call. sessionBias boosts entries from the current git branch. explain: true appendsmemory_forget — Lifecycle ops by key or id: action: "soft" (default) marks obsolete, "hard" permanently removes, "restore" brings back to active, "supersede"memory_stats — View memory state (including TTL stats, quality distribution, origin/status breakdown, cold memories below quality/access thresholds, and **hit ratememory_summary — Save/retrieve file summariesmemory_archive — Archive old entries (>30 days) and expired TTL entriesmemory_diff — Show changes since a date (24h, 7d, or exact date)memory_suggest — Find related entries for a given contextmemory_encrypt — Enable AES-256-GCM encryptionmemory_decrypt — Disable encryptionmemory_backup — Create timestamped backup of memory file (auto-prunes to 10 most recent)Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Toon Memory's toolset — memory_remember, memory_recall, memory_smart_recall and 11 more — is a fair guide to whether it matches your workflow. It is maintained by LuiggiVal08; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| memory_remember | Save a decision, pattern, bug, knowledge, or **warning** (negative "do NOT do this" memory, recalled with a boost) — optional TTL, auto-tag inference, links to build the memory graph, merge-dedup on same key, auto qualit |
| memory_recall | Search memory (use BEFORE reading files, filters expired TTL). mode: "graph" expands a relationship-aware subgraph for higher precision. budget: "tiny" |
| memory_smart_recall | **Unified recall**: BM25 + graph + decay + quality in one call. sessionBias boosts entries from the current git branch. explain: true appends per-entry reasons, budget_tokens caps output by estimated tokens. Use at the S |
| memory_forget | **Lifecycle ops** by key or id: action: "soft" (default) marks obsolete, "hard" permanently removes, "restore" brings back to active, "supersede" retires it with a superseded_by link to new_key |
| memory_stats | View memory state (including TTL stats, quality distribution, origin/status breakdown, cold memories below quality/access thresholds, and **hit rate / duplicate / obsolete** metrics) |
| memory_summary | Save/retrieve file summaries |
| memory_archive | Archive old entries (>30 days) and expired TTL entries |
| memory_diff | Show changes since a date (24h, 7d, or exact date) |
| memory_suggest | Find related entries for a given context |
| memory_encrypt | Enable AES-256-GCM encryption |
| memory_decrypt | Disable encryption |
| memory_backup | Create timestamped backup of memory file (auto-prunes to 10 most recent) |
| memory_captured | List activity auto-captured by hooks (opt-in) or clear the log |
| memory_checkpoint | **Session checkpoint**: creates a snapshot of current memory state with 7d TTL. Useful for rollback reference during long sessions |
{
"mcpServers": {
"toon-memory": {
"command": "npx",
"args": ["-y", "toon-memory"],
"env": {
"GITHUB_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GITHUB_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.