Skip to content
Agent Search Engine.

The shortlist

Give your AI agent long-term memory

Most agents forget everything when a session ends. A memory layer stores what the agent learns and brings the relevant parts back later. The options range from a library you build into your own agent to plain files your coding assistant can read.

3 picks · chosen editorially from the index · how we choose

For your own agents

Developer — library or service

mem0Infrastructure

66k stars · Open source · Python

The most-starred memory layer in the index, used to add persistent memory across sessions and users to agents you are building.

Watch outYou only need simple conversation history in a single session.

Memory you can read

Config entry — uvx

Basic MemoryMCP server

4.0k stars · Open source · Python

Stores what the assistant learns as local Markdown notes linked into a knowledge graph, which you can open and edit yourself, and works with Claude, Codex, Cursor and ChatGPT.

Watch outYour organisation can't adopt AGPL-3.0 software.

For coding agents

Install — Homebrew binary

EngramMCP server

6.8k stars · Open source · Go

Project memory for coding agents in a single Go binary with SQLite full-text search, exposed over MCP, with no Node.js, Python or Docker to install.

Before you commit

Memory is where agents quietly go wrong: a mistaken fact saved once gets retrieved and repeated for months. Prefer stores you can inspect and correct, keep personal or client data out unless you control where it is kept, and prune what the agent has saved from time to time.

For agent buildersMake your product part of the discovery.Explore advertising

More decisions