Project-local MCP memory server for AI coding agents. Knowledge graph stored in.mcp/ inside each repo — isolated per...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
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 unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Cursor AI
Model
Multiple
Fastest way to find out if n2n-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 n2n-memory -- npx n2n-memoryRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove n2n-memoryNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ n2n-memory ← registers here
Project-local MCP memory server for AI coding agents. Knowledge graph stored in.mcp/ inside each repo — isolated per project, Git-friendly JSON, dual-buffer (durable graph + active context).
Source: GitHub repository
Source check: October 27, 2026
Upstream commit: October 27, 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.