Memory Engine MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 22 Oct 2026.
Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const dest = path.join(backupDir, "memory-backup-" + ts + (a.label ? "-" + a.label : "") + ".db");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Memory Engine MCP
same job, measured the same wayPersistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
Embedded memory for AI agents with SQLite, pgvector, and Neo4j graph search.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Local-first AI memory cartridge with persistent MCP memory for Claude via SQLite FTS5.
Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
Cross-session memory for AI coding agents via six tools; local-first SQLite store.
Memory for AI assistants in one SQLite file: full-text search, no vectors, no embeddings.
Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
Memory Engine MCP — questions
Answers built from our own checks of this server.