Local-first Memory Framework for AI Agents · 99.2% LongMemEval-S retrieval @ k=10 · Supports Claude · Antigravity · L...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Claude
Fastest way to find out if m3-memory belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add m3-memory -- npx m3-memoryRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove m3-memoryNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ m3-memory ← registers here
Local-first Memory Framework for AI Agents · 99.2% LongMemEval-S retrieval @ k=10 · Supports Claude · Antigravity · LangChain · Hermes · Gemini · OpenCode · OpenClaw · MCP-native and plugins · Hybrid search (FTS5 + vector + MMR) · GDPR · FIPS 140-3 ready · 100% local (fully offline) or cloud capable
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 17, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.