leteo vs MCP AutoMem
leteo is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
leteo is a plugin bundle for AI coding tools published by Alexis Sanabria Lopez. No marketplace we read lists it any more. MCP AutoMem is an MCP server published by verygoodplugins. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MCP AutoMem | |
|---|---|---|
| Community marketplace asanabrial/leteo | Removed on 2026-10-17 Version: 0.3.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (npm): 793 Downloads/week (npm): 89 Forks (GitHub): 15 Stars (GitHub): 65 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | leteono longer listed · | MCP AutoMem |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 65 |
| Forks (GitHub) (differs) | 1 | 15 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@verygoodplugins/mcp-automem) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | 2 |
| Parts of the bundle (differs) | 6 | 7 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/asanabrial/leteo | github.com/verygoodplugins/mcp-automem |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of leteo
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
engram io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
-
Persistent shared memory powered by Deeplake — captures all session activity and provides cross-session, cross-agent memory search
-
Local memory with full-text recall and a recall-and-save skill.
-
Secure, portable, cloud-persistent memory across every conversation. Store and retrieve your personal facts, decisions, tasks, goals, and notes. Accessible from any AI client…
-
The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes
-
Save 60-90% on LLM token costs with intelligent memory compression. agent-memory automatically compresses tool output into structured observations, shares context across agents…
What each says it does
leteo
Persistent memory with session tracking, compaction recovery, and a save protocol. Gives the agent a memory that survives across sessions.
MCP AutoMem
Graph-vector memory for AI assistants using FalkorDB and Qdrant
How to run each
leteo
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP AutoMem As a Claude Code plugin
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automemCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: leteo · What it can do: MCP AutoMem · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.