Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Persistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
MNEMON_DB_PATH, MNEMON_EMBEDDING_PROVIDER, MNEMON_EMBEDDING_API_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"mnemon": {
"command": "npx",
"args": [
"-y",
"mnemon-mcp"
],
"env": {
"MNEMON_DB_PATH": "your-value",
"MNEMON_EMBEDDING_PROVIDER": "your-value",
"MNEMON_EMBEDDING_API_KEY": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add mnemon --env MNEMON_DB_PATH=your-value --env MNEMON_EMBEDDING_PROVIDER=your-value --env MNEMON_EMBEDDING_API_KEY=your-value -- npx -y mnemon-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"mnemon": {
"command": "npx",
"args": [
"-y",
"mnemon-mcp"
],
"env": {
"MNEMON_DB_PATH": "your-value",
"MNEMON_EMBEDDING_PROVIDER": "your-value",
"MNEMON_EMBEDDING_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"mnemon": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mnemon-mcp"
],
"env": {
"MNEMON_DB_PATH": "your-value",
"MNEMON_EMBEDDING_PROVIDER": "your-value",
"MNEMON_EMBEDDING_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
MNEMON_DB_PATH envMNEMON_EMBEDDING_PROVIDER envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub nikitacometa, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: MNEMON_EMBEDDING_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.0.1) llegó al registro hace 8 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Context7, Codebase Memory, Exa
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Persistent layered memory for AI agents. Local-first. Zero-cloud. Single SQLite file.
Landing Page · npm · GitHub
Your AI agent forgets everything after each session. Mnemon fixes that.
It gives any MCP-compatible client — OpenClaw, Claude Code, Cursor, Windsurf, or your own — a structured long-term memory backed by a single SQLite database on your machine. No API keys, no cloud, no telemetry. Just npm install and your agent remembers.
Flat key-value stores treat "what happened yesterday" the same as "never commit without tests." That's wrong — different kinds of knowledge have different lifetimes and access patterns.
Mnemon organizes memories into four layers:
| Layer | What it stores | How it's accessed | Lifetime |
|---|---|---|---|
| Episodic | Events, sessions, journal entries | By date or period | Decays (30-day half-life) |
| Semantic | Facts, preferences, relationships | By topic or entity | Stable |
| Procedural | Rules, workflows, conventions | Loaded at startup | Rarely changes |
| Resource | Reference material, book notes | On demand | Decays slowly (90 days) |
A journal entry from last Tuesday and a coding rule that never changes live in different layers — because they should.
Retrieval is measured against a 50-case golden set on a real 797-memory bilingual (RU/EN) corpus, through the actual MCP server — not a reimplementation. Current numbers (methodology & history):
| Metric | FTS-only | Vector-only | Hybrid (RRF) |
|---|---|---|---|
| Composite score | 88.9 | 89.2 | 91.7 |
| Recall@5 | 0.907 | 0.898 | 0.919 |
| MRR | 0.817 | 0.832 | 0.878 |
| nDCG@5 | 0.816 | 0.828 | 0.869 |
| Negative precision | 1.000 | 1.000 | 1.000 |
Hybrid beats both legs individually, which is the whole argument for fusing them: lexical search has the better raw recall, vector search the better ranking, and RRF keeps both instead of averaging them away.
The eval doc tracks the failures too — score drift under corpus growth, the BM25 field-weight bug the eval caught, the two cases where fusion still loses to pure lexical search, and what the golden set does *not* cover. Numbers you can't audit are marketing; read how these are produced.
flowchart LR
C["MCP client Claude Code · Cursor · …"] -- "stdio / HTTP" --> T["10 tools · 4 resources · 3 prompts"] T --> R["retrieval pipeline FTS5 · vector · RRF fusion"] T --> M["memories + supersede chains"] I["KB import pipeline markdown → memories"] --> M M -- triggers --> F["FTS5 index (stemmed EN+RU)"] R --> F R --> V["sqlite-vec (optional, BYOK)"]
One SQLite file holds memories, the FTS5 index, and the optional vector index. Writes go through transactions that keep the supersede-chain invariant; reads run the staged retrieval pipeline described under Search.
The full picture — module boundaries, write/read paths, invariants, and known limitations — is in docs/ARCHITECTURE.md. Design decisions are recorded as ADRs: SQLite+FTS5 core, hybrid RRF retrieval, synchronous driver, layered memory model.
npm install -g mnemon-mcp
Or from source:
git clone https://github.com/nikitacometa/mnemon-memory-mcp.git
cd mnemon-memory-mcp && npm install && npm run build
OpenClaw
openclaw mcp register mnemon-mcp --command="mnemon-mcp"
Or add to ~/.openclaw/mcp_config.json:
{
"mnemon-mcp": { "command": "mnemon-mcp" } }
Claude Code
Add to ~/.claude/mcp.json:
{
"mcpServers": { "mnemon-mcp": { "command": "mnemon-mcp" } } }
Cursor / Windsurf / Other MCP clients
Add to your client's MCP config:
{
"mcpServers": { "mnemon-mcp": { "command": "mnemon-mcp" } } }
Running from source?
Use the full path to the compiled entry point:
{
"mnemon-mcp": { "command": "node", "args": ["/absolute/path/to/mnemon-mcp/dist/index.js"] } }
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | mnemon-mcp
You should see 10 tools in the response. The database (~/.mnemon-mcp/memory.db) is created automatically on first run.
That's it. Your agent now has persistent memory.
| Tool | What it does |
|---|---|
| `memory_add` | Store a memory with layer, entity, confidence, importance, and optional TTL |
| `memory_search` | Full-text or exact search with filters by layer, entity, date, scope, confidence |
| `memory_update` | Update in-place or create a versioned replacement (superseding chain) |
| `memory_delete` | Delete a memory; re-activates its predecessor if any |
| `memory_inspect` | Get layer statistics or trace a single memory's version history |
| `memory_export` | Export to JSON, Markdown, or Claude-md format with filters |
| `memory_health` | Run diagnostics: expired entries, orphaned chains, stale memories; optionally GC |
| `memory_session_start` | Start an agent session — returns session ID for grouping memories |
| `memory_session_end` | End a session with optional summary; returns duration and memory count |
| `memory_session_list` | List sessions with filters by client, project, or active status |
Resources — live data your agent can read:
| URI | Returns |
|---|---|
memory://stats | Aggregate stats per layer |
memory://recent | Memories created/updated in last 24h |
memory://layer/{layer} | All active memories in a layer |
memory://entity/{name} | All active memories about an entity |
Prompts — pre-built workflows:
| Prompt | Purpose |
|---|---|
recall | "Tell me everything you know about X" |
context-load | Load relevant context before starting a task |
journal | Create a structured journal entry |
Four modes, all supporting layer / entity / scope / date / confidence filters:
FTS mode (default without embeddings) — tokenized full-text search with BM25 ranking. Multi-word queries use AND; if too few results, OR supplements with a score penalty. Progressive AND relaxation tries top-3 most specific terms before falling back to full OR.
Hybrid mode (default when embeddings configured) — combines FTS5 + vector search via Reciprocal Rank Fusion. Detects quoted entities in queries (e.g., 'Essentialism') and runs weighted sub-queries for cross-reference retrieval.
Vector mode — pure cosine similarity search over embeddings.
Exact mode — LIKE substring match for precise phrase lookups.
Scores: bm25 × (0.3 + 0.7 × importance) × decay(layer) × recency
Recency boost: 1 / (1 + daysSince / 365) — gently rewards recently created memories without penalizing old ones.
Snowball stemmer applied at both index time and query time for English and Russian. This means "running" matches "runs", and "книги" matches "книга". Stop words are filtered from queries to improve precision.
Knowledge evolves. Mnemon doesn't delete old facts — it chains them:
v1: "Team uses React 17" → superseded_by: v2
v2: "Team uses React 19" → supersedes: v1 (active)
Search returns only the latest version. memory_inspect with include_history: true reveals the full chain. memory_delete re-activates the predecessor — nothing is lost.
Enable semantic similarity search by providing your own embedding API:
# OpenAI
MNEMON_EMBEDDING_PROVIDER=openai MNEMON_EMBEDDING_API_KEY=sk-... mnemon-mcp
MNEMON_EMBEDDING_PROVIDER=ollama mnemon-mcp
This unlocks two additional search modes:
Requires sqlite-vec (installed as optional dependency). New memories are embedded on add; existing ones can be backfilled.
Embedding configuration
| Variable | Default | Description |
|---|---|---|
MNEMON_EMBEDDING_PROVIDER | — | openai or ollama (unset = disabled) |
MNEMON_EMBEDDING_API_KEY | — | API key (required for OpenAI) |
MNEMON_EMBEDDING_MODEL | text-embedding-3-small / nomic-embed-text | Model name |
MNEMON_EMBEDDING_DIMENSIONS | 1024 / 768 | Vector dimensions |
MNEMON_OLLAMA_URL | http://localhost:11434 | Ollama endpoint |
Got a folder of Markdown files? Import them in bulk:
cp config.example.json ~/.mnemon-mcp/config.json # edit this first
npm run import:kb -- --kb-path /path/to/your/kb # incremental (skips unchanged files)
The config maps glob patterns to memory layers:
{
"owner_name": "your-name", "extra_stop_words": [], "mappings": [ { "glob": "journal/*.md", "layer": "episodic", "entity_type": "user", "entity_name": "$owner", "importance": 0.6, "split": "h2" }, { "glob": "people/*.md", "layer": "semantic", "entity_type": "person", "entity_name": "from-heading", "importance": 0.8, "split": "h3" } ] }
| Field | Type | Description |
|---|---|---|
owner_name | string | Your name — used for $owner substitution in entity_name |
extra_stop_words | string[] | Words to filter from FTS queries (e.g., your name forms) |
glob | string | File pattern to match |
layer | string | Target memory layer |
entity_type | string | user / person / project / concept / file / rule / tool |
entity_name | string | Literal name, "$owner", or "from-heading" (extract from H2/H3) |
split | string | "whole" (one memory per file), "h2", or "h3" (split on headings) |
importance | number | 0.0–1.0, affects search ranking |
confidence | number | 0.0–1.0, filterable in search |
scope | string | Optional namespace |
For remote or multi-client setups:
MNEMON_AUTH_TOKEN=your-secret MNEMON_HOST=0.0.0.0 MNEMON_PORT=3000 npm run start:http
| Endpoint | Description |
|---|---|
POST /mcp | MCP JSON-RPC (Bearer auth if token set) |
| GET /health | `{"status":"o
Solo se muestra el principio; lee el resto en el repo