Log inSubmit server
Leteo logo

Leteo

Local SQLite memory for coding agents, exposed through one Leteo binary and 22 MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Leteo

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "leteo": {
      "command": "bunx",
      "args": [
        "@asanabrial/leteo"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Leteo MCP server gives coding agents persistent project memory through a local SQLite database. It stores decisions, fixes, conventions, and discoveries, then makes relevant entries available in later sessions through 22 MCP tools. The single Rust binary runs locally without a separate server or API key, making it suitable for agents that need continuity across sessions. Reach for it when context compaction or new sessions cause an agent to lose project-specific knowledge.

Use cases

  • Preserve project decisions across coding-agent sessions
  • Retrieve prior bug fixes and conventions during development
  • Browse stored agent memories in a terminal UI
  • Export or delete a project's local memory
  • Configure persistent memory for supported coding agents

Key features

  • Local SQLite-backed persistent memory
  • 22 MCP tools
  • Single Rust binary
  • Terminal UI for memory browsing
  • Project-specific memory
  • Optional cloud replication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @asanabrial/leteo (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads815Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Leteo works

What Leteo MCP server does

Leteo MCP server adds persistent memory to AI coding agents. It records information such as implementation decisions, resolved bugs, project conventions, and non-obvious findings in a SQLite database stored on the local machine. The agent can use that memory in later sessions instead of rediscovering the same project details.

The database belongs to the user and can be inspected with Leteo's terminal interface. leteo tui opens a dashboard for browsing and narrowing memories, while leteo export provides a way to take the stored data elsewhere. leteo delete removes it. Cloud replication can be enabled for a project, but the default design is local storage.

How it works

Leteo runs as one compiled Rust executable. SQLite is included in the binary, so a separate database server, SQLite installation, runtime, or API key is not required. The MCP connection is configured for an agent through Leteo's setup flow, and the agent can save and retrieve memories during its work.

The intended workflow is implicit rather than prompt-driven: an agent begins a session with relevant project knowledge and records useful discoveries as it works. The stored notes are written for future agent sessions and are kept separate from the normal conversation context.

Leteo MCP server is designed for local operation on Linux, macOS, and Windows. The repository provides prebuilt binaries for x86-64 Linux, Windows, and macOS, plus arm64 Linux and macOS builds. The documented Windows target is Windows 10 or later; the Linux releases require glibc 2.34 or newer.

Setup and configuration

Installers are available through shell and PowerShell scripts, Homebrew, Scoop, winget, and npm. Source installation is also available with Cargo. Release archives include the SQLite-enabled executable, so most installation paths do not require Rust. Building from source requires Rust and Cargo.

After installation, run leteo tui and use the Setup screen to configure an agent. A source build can rerun setup for agents that already have Leteo configured, because the MCP entry must point to the new executable path.

The installer scripts accept LETEO_INSTALL_DIR, LETEO_VERSION, and LETEO_BASE_URL. These variables control installation behavior rather than the running MCP process. A source checkout can use LETEO_SETUP_AGENTS to provide a space-separated list of agents for setup.

Tools and capabilities

  • Provides 22 MCP tools for agent-facing memory operations.
  • Persists memories in a local SQLite database.
  • Supports project-specific knowledge across agent sessions.
  • Includes a terminal UI for browsing and searching stored memories.
  • Exports or deletes the local memory store.
  • Supports optional cloud replication for a named project.

Limitations and notes

Leteo is focused on persistent memory for coding agents, not general-purpose database administration.

The repository's measurement notes report mixed token results and explicitly caution that Leteo does not reliably reduce token use. Its stated purpose is to preserve project knowledge and reduce confidently incorrect answers when the code alone does not contain the needed context. The npm installation route cannot configure an agent through leteo setup; the README directs users to configure the agent with the npx line or use another installation method.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Leteo

Leteo is an MCP server that connects AI coding agents to a local SQLite memory database. Its 22 MCP tools let agents preserve and retrieve project knowledge such as decisions, bug fixes, conventions, and discoveries across sessions. It runs as a single Rust binary without a separate database server or API key.

Install Leteo with the Linux or macOS script, the Windows PowerShell script, Homebrew, Scoop, winget, npm, or Cargo. Then run `leteo tui` and configure an agent from the Setup screen. Prebuilt releases include SQLite and do not require Rust or a separate runtime.

Yes, Leteo lists Cursor among its supported coding-agent clients. Install the binary, open `leteo tui`, and use the Setup screen to configure the agent.

Leteo stores memory in a local SQLite database owned by the user. The default setup keeps data on the local machine, and the terminal UI can browse it.

No, Leteo does not require an API key or a separate database server. It is distributed as one binary with SQLite compiled in, so standard release installations do not need SQLite, Rust, or another runtime installed first.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLeteo AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/leteo?style=directory)](https://allmcps.com/mcp/leteo)
HTML Embed
<a href="https://allmcps.com/mcp/leteo"><img src="https://allmcps.com/api/badge/leteo?style=directory" alt="Leteo on AllMCPs" /></a>