Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
File-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB.
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.
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": {
"memory-fabric": {
"command": "uvx",
"args": [
"memory-fabric"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add memory-fabric -- uvx memory-fabricPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"memory-fabric": {
"command": "uvx",
"args": [
"memory-fabric"
]
}
}
}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": {
"memory-fabric": {
"type": "stdio",
"command": "uvx",
"args": [
"memory-fabric"
]
}
}
}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.
Esta 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 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub elViRafa, 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.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
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.4.5) llegó al registro hace 4 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) 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.
File-first, local-first memory layer for MCP-compatible AI coding assistants.
Memory Fabric gives AI tools like Claude Code, Cursor, and GitHub Copilot a consistent, project-aware context layer without locking you into one model, editor, cloud provider, or operating system.
Memory is stored as human-readable Markdown with YAML frontmatter. No vector database. No cloud account. No embeddings required.
memory-store/, one per file; root maps (architecture.md, decisions.md, ...) are generated views rebuilt by Dreaming, never hand-writtenai-memory verify flags citations that rottedwrite_failure_memory_tool deduplicates repeat occurrences of the same error into one growing record instead of scattering near-duplicatesrg, git hooks, or Dreaming configuredv1.4.5 — field diary pack/analyze and live posture pinning. [Live on PyPI](https://pypi.org/project/memory-fabric/). Core CLI and MCP tools work end-to-end. See ROADMAP.md for what shipped, what's in progress, and what's next.
The CLI and self-capture flow: initialize a project, write a memory as a plain Markdown file in your repo, and watch a git commit record itself as episodic memory with no agent cooperation. The cross-tool moment — an agent writes memory in one tool and a different tool reads it back — is storyboarded in DEMO.md for the full video.
Memory Fabric never sends data anywhere. There is no account, no cloud, no analytics, no phone-home. The core read and write paths make no network calls at all; the only optional network requests are a PyPI version-drift check and an LLM-provider preflight, both of which you can turn off with --offline. Your memory is plain Markdown in your own git history — it never leaves your machine unless you push it.
An optional, off-by-default field diary can record operational counts on your machine after you run ai-memory diary approve. That is not the session journal, and it is not telemetry: nothing is transmitted. MEMORY_FABRIC_DIARY=0 is a kill switch. ai-memory diary pack builds a shareable folder under the app data field-packs/ directory (Windows: %APPDATA%/memory-fabric/field-packs/); you copy that folder yourself. ai-memory diary analyze scores product signals from a pack or the local diary. This is a deliberate guarantee, not a default we might change.
Requires Python ≥ 3.11.
pipx install memory-fabric # CLI only
pipx install "memory-fabric[mcp]" # CLI + MCP server
Or with plain pip (inside a virtual environment):
pip install memory-fabric # CLI only
pip install "memory-fabric[mcp]" # CLI + MCP server
Zero-install one-off run (requires uv):
uvx --from "memory-fabric[mcp]" memory-fabric-mcp # starts the MCP server on stdio
# CLI only
pipx install "git+https://github.com/elViRafa/agentic-memory.git"
pipx install "memory-fabric[mcp] @ git+https://github.com/elViRafa/agentic-memory.git"
Or with plain pip (inside a virtual environment):
pip install "git+https://github.com/elViRafa/agentic-memory.git" # CLI only
pip install "memory-fabric[mcp] @ git+https://github.com/elViRafa/agentic-memory.git" # + MCP
Because Memory Fabric is in active development, we recommend upgrading regularly:
# If installed via pipx:
pipx upgrade memory-fabric
pip install --upgrade "memory-fabric[mcp]"
pipx install --force "memory-fabric[mcp] @ git+https://github.com/elViRafa/agentic-memory.git"
uvx (the default written by older ai-memory install runs), uv serves the build it cached the first time and never re-resolves an unpinned spec — restarting the client is not enough and can leave the server several releases behind without any signal. After upgrading, either: # Re-write the client config (now pins the exact installed version, or points
ai-memory install --client --project
uv cache clean memory-fabric
`ai-memory doctor` warns when the local version drifts from the latest on PyPI or
when a different ai-memory installation shadows this one on PATH.
memory-fabric-mcp server. ai-memory init --install-hooks
This will safely refresh starter templates and local git hook integration to the latest format without overwriting your existing memory markdown files.
Windows terminals: the CLI emits UTF-8 (memory content legitimately contains
em-dashes and bullets). Windows Terminal and PowerShell 7 render it out of the box;
on legacy consoles (PowerShell 5.1 with an OEM code page) set
chcp 65001or
PYTHONUTF8=1if you see replacement characters.
Or clone and install in editable mode for local development:
git clone https://github.com/elViRafa/agentic-memory.git
cd agentic-memory pip install -e . # CLI only pip install -e ".[mcp]" # CLI + MCP server
ai-memory init
Creates .ai-memory/ in the current directory with starter sections and a .gitignore.
ai-memory doctor
ai-memory eval
ai-memory eval --json
eval scores whether memories are useful for coding assistants. It checks section coverage, starter-template content, summary quality, metadata, retrieval readiness, and likely secrets.
If .ai-memory/ exists, reports are saved under ignored local files:
.ai-memory/evals/latest.json
.ai-memory/evals/latest.md .ai-memory/evals/ -memory.json .ai-memory/evals/ -memory.md
If .ai-memory/ does not exist yet, eval prints a pre-init report only and creates no files.
ai-memory query "authentication"
ai-memory dream --mode light
ai-memory dream --mode deep
Dreaming creates a snapshot before maintenance. You can evaluate whether a Dreaming run improved memory quality:
ai-memory eval --dream latest
ai-memory dream --mode light --eval
Dream eval compares the pre-dream snapshot to current memory and reports score delta, changed files, improvements, and regressions.
One command per client. Safe to re-run: merges with your existing config, never overwrites it, and backs up the original file if it can't be parsed.
These call uvx --from "memory-fabric[mcp]" memory-fabric-mcp under the hood — same canonical invocation as ai-memory install, just without the CLI step. Requires uv.
| Client | Command |
|---|---|
| Claude Code | ai-memory install --client claude-code |
| Claude Desktop | ai-memory install --client claude-desktop |
| VS Code | ai-memory install --client vscode |
| Cursor | ai-memory install --client cursor |
| Windsurf | ai-memory install --client windsurf |
| Codex | ai-memory install --client codex |
| Antigravity | ai-memory install --client antigravity |
| Gemini CLI | ai-memory install --client gemini-cli |
| Cline | ai-memory install --client cline |
| All detected clients | ai-memory install --client all |
Add --project to write project-scoped config instead of the global/user config (where the client supports it). Add --dry-run to preview the change as a unified diff without writing anything. Add --uninstall to remove only the memory-fabric entry, leaving everything else in the file untouched.
| Tool | Description | |
|---|---|---|
initialize_memory_fabric_tool | Create .ai-memory/ scaffolding in a project | |
read_combined_context_tool | Load Tier 0 directives + prioritized memory within token budget | |
read_section_tool | Read a single memory section by name | |
keyword_search_tool | Search memory with ripgrep or Python fallback | |
write_local_memory_tool | Update steering sections (framework-rules, ubiquitous-language) only. Writing facts or root maps is rejected (store-first) — root maps are generated from memory-store/; use write_memory_store_tool | |
propose_memory_patch_tool | Preview proposed memory changes without applying | |
dream_tool | Run memory maintenance / consolidation (--mode light | deep) |
prepare_dream_payload_tool | Prepare candidate snapshot and return consolidation prompt for client-driven dreaming | |
apply_dream_results_tool | Apply LLM consolidated JSON output to candidate snapshot and save changes | |
evaluate_memory_fabric_tool | Evaluate local memory quality | |
evaluate_dream_quality_tool | Evaluate a Dreaming run against a snapshot | |
write_memory_store_tool | Write a memory file to a semantic store path (e.g. architecture/decisions/auth); accepts an optional evidence citation list |
Solo se muestra el principio; lee el resto en el repo