Memkeeper runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Aug 2026.
Local-first memory for AI agents: on-device hybrid retrieval over a single SQLite file.
What the code does
We read the source, 20 h ago · rules 3dff92dd89df
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 child = spawn(this.binary, ["serve", "--stdio"], {
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 Memkeeper
same job, measured the same wayEmbedded, local-first memory and retrieval for AI agents. One SQLite file, no server, no API key.
Token-light local memory with SQLite hybrid retrieval for MCP agents.
Local-first memory for coding agents — MCP server, single SQLite file, local embeddings
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Durable memory for AI agents: fact extraction, hybrid retrieval, temporal graph. SQLite/Postgres.
Local-first agent memory over SQLite: remember, recall, link, forget. Degrades, never fails.
Keyword, semantic, hybrid, and SQL retrieval for AI agents, local or on Infino Cloud.
Local memory for AI agents. One SQLite file on your machine — no cloud, no account.
Memkeeper — questions
Answers built from our own checks of this server.