Leteo runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Sep 2026.
Persistent memory for AI coding agents: one Rust binary, one local SQLite database.
What the code does
We read the source, 13 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.
execFileSync(tar, ["-xf", archivePath, "-C", into], {
const archivePath = path.join(staging, archiveName);
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 Leteo
same job, measured the same wayLocal-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.
Local MCP memory for coding agents. SQLite on your machine — preferences persist across chats.
Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
Persistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud.
Local long-term memory MCP server (SQLite) for AI coding agents — OpenCode, Claude Code, Cursor
Persistent semantic memory for SQL databases. Postgres, MySQL, MSSQL, SQLite.
Leteo — questions
Answers built from our own checks of this server.