mcpbeat Sign in

Leteo MCP Server

by asanabrial Your server? Claim it
local only

Leteo runs on your own machine — the client starts it, so there is no endpoint to ping. 116 installs a week from npm. Last commit 15 Oct 2026.

Persistent memory for AI coding agents: one Rust binary, one local SQLite database.

Installs per day peak 64 · avg 10 · +175% w/w
a month agotoday
116
Installs / week
npm · @asanabrial/leteo
2
Stars
2 open issues
15 Oct 2026
Last commit
5 releases in 90 days
MIT
License
Rust

What the code does

We read the source, 23 h ago · rules ccca72095570

Capabilities

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);
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        r = subprocess.run([self.binary, "--version"], capture_output=True, text=True, env=dict(os.environ))

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.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add leteo -- npx -y @asanabrial/leteo
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "leteo": {
      "args": [
        "-y",
        "@asanabrial/leteo"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.leteo]
command = "npx"
args = ["-y", "@asanabrial/leteo"]
.cursor/mcp.json
{
  "mcpServers": {
    "leteo": {
      "args": [
        "-y",
        "@asanabrial/leteo"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "leteo": {
      "args": [
        "-y",
        "@asanabrial/leteo"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: LETEO_DATA_DIR (Where the database lives. Defaults to ~/.leteo, and only needs setting for a store kept somewhere else — the server is started by the agent rather than by a person, so it cannot inherit a shell's environment.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Leteo

same job, measured the same way
repo-memory-mcp
by umarjaum

Persistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.

183 installs/wk local only
sync82
by oito2

Persistent, structured project memory for AI coding agents, stored locally in SQLite.

local only
Engram
by hbarefoot

Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.

46 installs/wk local only
remem-mcp — Local-first MCP Memory + CodeGraph + Wiki
by tinhien11

Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.

130 installs/wk local only
dark-memory-mcp
by opita-code

Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.

281 installs/wk local only
memex
by kioie

Local MCP memory for coding agents. SQLite on your machine — preferences persist across chats.

local only
SAME - Stateless Agent Memory Engine
by sgx-labs

Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.

46 installs/wk local only
LoreConvo
by labyrinth-analytics

Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.

892 installs/wk local only

Leteo — questions

Answers built from our own checks of this server.

Why is there no uptime for Leteo?
Leteo runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @asanabrial/leteo was installed 116 times last week.
How do I connect Leteo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @asanabrial/leteo straight from npm; nothing to host, nothing to sign up for.
How many people use Leteo?
The npm package @asanabrial/leteo was installed 116 times in the last week. Week over week that is +175%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Leteo open source?
Yes — it is published under the MIT licence, written in Rust, 2 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.