# flywheel-memory

> MCP server giving AI a knowledge graph over Obsidian vaults. 13-layer scoring that learns. Local-first, zero cloud.

- **URL**: https://www.freshcrate.ai/projects/flywheel-memory
- **Author**: velvetmonkey
- **Category**: MCP Servers
- **Latest version**: `flywheel-memory-v2.12.16` (2026-06-07)
- **License**: Apache-2.0
- **Source**: https://github.com/velvetmonkey/flywheel-memory
- **Language**: TypeScript
- **GitHub**: 7 stars, 6 forks
- **Registry**: github (`velvetmonkey/flywheel-memory`)
- **Tags**: `ai-tools`, `backlinks`, `benchmark`, `claude`, `claude-desktop`, `hotpotqa`, `knowledge-graph`, `local-first`, `model-context-protocol`, `typescript`

## Description

MCP server giving AI a knowledge graph over Obsidian vaults. 13-layer scoring that learns. Local-first, zero cloud.

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `flywheel-memory-v2.12.16` | 2026-06-07 | High | CI green again (first since 2026-05-29). Kills the vault-core registry-shadow class permanently (core versioned past the frozen registry → workspace-link forced), fixes the salvage fixture, converts package-startup to the dual-tarball git-clone smoke, repairs the graph benchmark (real demo vault + recalibrated ceilings), adds the local-deploy TOC, skips the POSIX chmod guard test on Windows, and rewrites install docs to git-clone-only. Includes #377's wikilinker-escape fix in the first restarted |
| `flywheel-memory-v2.12.12` | 2026-05-11 | High | ## What's New  **Bug fix release** — resolves FTS5 column-injection failures observed in production scheduled jobs on 2026-05-10.  - **fix(fts5): apply escapeFts5Query to memory + similarity + note search** (#358)   - `core/write/memory.ts` — wrap raw user query with `escapeFts5Query` before `memories_fts MATCH ?`; widen catch to intercept `no such column` so future bypasses surface as `Invalid search query` instead of leaking raw SQL.   - `core/read/fts5.ts` — retire local `sanitizeFTS5Query` ( |
| `flywheel-memory-v2.12.8` | 2026-05-04 | High | ## What's New  Patch fix: restore the per-note `signals` block in `insights(action: 'staleness')`.  - **#346** — The signals block (`backlink_count`, `hub_score`, `outlink_count`, `has_open_tasks`, `status_active`, `active_entity_ratio`) was dropped during the T43 tool collapse when `predict_stale_notes` folded into `insights`. flywheel-crank's Stale Notes panel crashed with `Cannot read properties of undefined (reading 'backlink_count')` against any 2.12.x server. Restored by porting back the o |
| `flywheel-memory-v2.12.5` | 2026-04-30 | High | ## What's New  - **Scoped private memory ownership** (#335) — memories can now be scoped to a specific owner/agent, isolating private memory streams. - **Fix integrity worker tsx loader resolution** (#333) — resolves loader path issues in worker thread spawn under tsx. - **Docs**: drop Flywheel Engine from Suite section (#334), README messaging refresh (#332).  **Full Changelog**: https://github.com/velvetmonkey/flywheel-memory/compare/flywheel-memory-v2.12.4...flywheel-memory-v2.12.5 |
| `flywheel-memory-v2.12.4` | 2026-04-21 | High | Release 2.12.4 of @velvetmonkey/flywheel-memory. Published to npm and verified with the post-publish Codex smoke test against @latest. |
| `flywheel-memory-v2.12.3` | 2026-04-20 | High | ## What's Changed * chore: ignore generated local memory artifacts by @velvetmonkey in https://github.com/velvetmonkey/flywheel-memory/pull/323 * Codex/p44 review followup hardening by @velvetmonkey in https://github.com/velvetmonkey/flywheel-memory/pull/324 * [codex] Update chat scoped session pool branch by @velvetmonkey in https://github.com/velvetmonkey/flywheel-memory/pull/325 * [codex] complete P44 phase E hardening by @velvetmonkey in https://github.com/velvetmonkey/flywheel-memory/pull/3 |
| `flywheel-memory-v2.12.2` | 2026-04-20 | High | ## Summary - release the P44 hardening train as `@velvetmonkey/flywheel-memory@2.12.2` - include multi-vault isolation hardening, policy/path-security hardening, and watcher lifecycle test expansion - include the Windows CI test portability fix needed for the merged train to stay green  ## Verification - `npm run build` - `npm run lint` - `npm pack --dry-run -w @velvetmonkey/flywheel-memory` - `npm run smoke:registry-latest -w @velvetmonkey/flywheel-memory` |
| `flywheel-memory-v2.12.1` | 2026-04-17 | High | ## Summary - ship the chat-scoped session isolation MCP support used by flywheel-engine - scope recent session brief context by agent_id to stop cross-chat bleed - keep the audit lockfile refresh included in the release branch  ## Verification - npm run build -w @velvetmonkey/vault-core - npm run lint in packages/mcp-server - npm run build in packages/mcp-server - npm run smoke:registry-latest -w @velvetmonkey/flywheel-memory |
| `flywheel-memory-v2.12.0` | 2026-04-13 | Medium | Release v2.12.0.\n\nChanges:\n- retire note_read alias; read is now canonical\n- surface graph(action: "export") explicitly in docs and generated tool contract\n- sync downstream pins in flywheel-engine, flywheel-demo, and flywheel-crank |
| `flywheel-memory-v2.11.3` | 2026-04-13 | Medium | Release @velvetmonkey/flywheel-memory v2.11.3. |

## Citation

- HTML: https://www.freshcrate.ai/projects/flywheel-memory
- Markdown: https://www.freshcrate.ai/projects/flywheel-memory.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/flywheel-memory/deps

_Generated by freshcrate.ai. Indexes github releases for AI-agent ecosystem packages._