Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Shared memory for coding agents: projects, reusable code, sessions and commits across machines
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.
CODEMEM_DATA, CODEMEM_DB, CODEMEM_HOST, CODEMEM_PORT, OLLAMA_URL, CODEMEM_EMBED, GIT_ROOTNecesitas
¿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": {
"codemem": {
"command": "uvx",
"args": [
"codemem-mcp",
"serve"
],
"env": {
"CODEMEM_DATA": "your-value",
"CODEMEM_DB": "your-value",
"CODEMEM_HOST": "your-value",
"CODEMEM_PORT": "your-value",
"OLLAMA_URL": "your-value",
"CODEMEM_EMBED": "your-value",
"GIT_ROOT": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add codemem --env CODEMEM_DATA=your-value --env CODEMEM_DB=your-value --env CODEMEM_HOST=your-value --env CODEMEM_PORT=your-value --env OLLAMA_URL=your-value --env CODEMEM_EMBED=your-value --env GIT_ROOT=your-value -- uvx codemem-mcp serveCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"codemem": {
"command": "uvx",
"args": [
"codemem-mcp",
"serve"
],
"env": {
"CODEMEM_DATA": "your-value",
"CODEMEM_DB": "your-value",
"CODEMEM_HOST": "your-value",
"CODEMEM_PORT": "your-value",
"OLLAMA_URL": "your-value",
"CODEMEM_EMBED": "your-value",
"GIT_ROOT": "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": {
"codemem": {
"type": "stdio",
"command": "uvx",
"args": [
"codemem-mcp",
"serve"
],
"env": {
"CODEMEM_DATA": "your-value",
"CODEMEM_DB": "your-value",
"CODEMEM_HOST": "your-value",
"CODEMEM_PORT": "your-value",
"OLLAMA_URL": "your-value",
"CODEMEM_EMBED": "your-value",
"GIT_ROOT": "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.
CODEMEM_DATA envCODEMEM_DB envCODEMEM_HOST envCODEMEM_PORT envOLLAMA_URL envCODEMEM_EMBED envGIT_ROOT 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 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub jeang42, 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 (0.1.0) llegó al registro hace 42 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.
Your coding agents keep rebuilding what you already have. codemem remembers what they built, across every project and every machine, and scores each piece on evidence of whether it worked.
It is an MCP server for Claude Code and other MCP clients. It knows what projects exist, where they live, what reusable pieces they contain, what each session did and decided, every commit pushed to the git host, and how to do recurring things. Everything is searchable from any machine, from an agent, or from the web UI. It is written to *during* work, not after.
One Python process, SQLite, no external services required.
Inventory scripts snapshot a directory and you read the report once. Registries list what people published. codemem does neither.
verify records "I ran it today and it works" and restarts the freshness clock. Scores are recomputed on every sync, so they decay when you stop touching something.authoritative, usable, experimental, antiquated, sunset, broken, junk, each with a reason. Search ranks by it, and you can exclude the ratings you should not build on.| Endpoint | What |
|---|---|
http:// :8055/mcp | MCP (streamable HTTP) for Claude Code and other MCP clients |
http:// :8055/ | Web UI: search, projects, assets, notes, activity, docs. Dark mode. |
http:// :8055/api/… | JSON API used by the UI (see docs/architecture.md) |
http:// :8055/health | liveness |
Normally runs on the git host, the machine holding the bare repos, so it can read them directly.
Security: codemem has no authentication. It is built for a trusted network, and anyone who
can reach the port can read and write everything. Do not expose it to the internet without an
authenticating proxy in front of it. See docs/architecture.md.
Python 3.11 or newer, and git. Optional: a git host with bare repos for the commit feed, Gitea for descriptions and web links, and Ollama for semantic search, drafted descriptions and the review pass. Everything works without the optional pieces; search falls back to BM25 alone.
A developer with many project folders across several machines has no way for a new Claude Code session to know that a retry wrapper, a Gradio helper, a GPU monitor or a data pipeline already exists somewhere. So they get rebuilt. Snapshot inventory scripts (run, read, forget) do not fix that. codemem is the live, writable layer: it is written to during work, not after.
The content is whatever is there. codemem does not filter or judge. Each project carries an audience: unrestricted (the default), professional, or employer, so a search or a view can exclude one when the context calls for it. Nothing is hidden unless asked, with one exception: cloned third-party repos are marked origin = vendor and stay out of search and lists until you ask for them. See docs/USER_GUIDE.md.
The package is codemem-mcp; the command it installs is codemem.
pip install codemem-mcp # or: uv tool install codemem-mcp / pipx install codemem-mcp codemem serve # MCP at http://localhost:8055/mcp, web UI at http://localhost:8055/
uvx codemem-mcp serve # or run it without installing
Data goes to ~/.codemem/ unless CODEMEM_DB or CODEMEM_DATA says otherwise. Register it with Claude Code:
claude mcp add --transport http --scope user codemem http://localhost:8055/mcp
That is the server alone. For the systemd units, the commit feed and the session hooks, use the quick start below from a clone of the repository.
docker build -t codemem . docker run --rm -p 127.0.0.1:8055:8055 codemem # throwaway database docker run -d -p 127.0.0.1:8055:8055 -v codemem-data:/data codemem # keep it in a volume
No authentication. Anyone who can reach the port can read and write everything. Keep the
127.0.0.1:in-p: a bare-p 8055:8055publishes the port on every interface, and Docker's
port rules bypass most host firewalls.
The image needs none of the optional pieces: embeddings are off (CODEMEM_EMBED=0) and there is no git host. Pass -e OLLAMA_URL=... -e CODEMEM_EMBED=1 to turn semantic search on.
Server (once, on the git host):
./install.sh # venv, user-scope systemd units, seed, backfill, gitea, scan, embed
Client (each machine, once):
CODEMEM_URL=http:// :8055 client/install-client.sh # Linux/macOS: MCP server + SessionStart/SessionEnd hooks client\install-client.ps1 # Windows PowerShell (set $env:CODEMEM_URL first)
Then in any Claude Code session the codemem tools are available and every session starts with a brief of the current project (if codemem knows it) and ends with an automatic session record.
| Tool | Use |
|---|---|
search | hybrid BM25 + embedding search over everything. First call before building anything |
project_brief | everything about one project, by name or working directory |
list_projects | filter by status, tag, machine, audience, visibility |
update_project | description, purpose, status, tags, audience, origin (own/vendor), visibility, maturity |
register_asset | record a reusable script/module/prompt/skill/service with a one-line usage |
find_assets | search or list assets by kind/tag/project, or by imported library |
log_session | what was done, decided, used, abandoned, and what is next |
add_note | decision, howto, resource, issue, idea |
delete_note | remove a note written by mistake, with its index and embedding rows |
link_items | project uses / could-reuse / supersedes / derived-from another |
rate | maturity: authoritative, usable, experimental, antiquated, sunset, broken, junk, with a why |
verify | "I ran it today and it works": restarts the computed trust score's freshness clock |
handoff / list_handoffs | track one implementation replacing another through candidate, shadow, verified, promoted |
howto | how to publish, add a machine, use codemem, plus whatever docs are ingested |
activity | commits and sessions across all machines, last N days |
add_scan_root / scan_path | register a directory to scan; scan now (server machine) |
stats | counts, machines, index coverage |
help | workflow, tool list, label vocabularies. Also /codemem in Claude Code, /codemem searches |
GIT_ROOT is backfilled; a post-receive hook posts each push to /ingest/push so new commits appear within seconds. See docs/git-commit-feed.md.client/codemem_agent.py once a root is registered.auto-discovered assets, with shared-code links between repos.CODEMEM_DOC_SOURCES (this repo by default), re-hashed every sync.codemem/ the server package config.py every tunable, env-overridable db.py schema, connection, single FTS5 index store.py all writes (keeps the index in step) search.py BM25 + Ollama embeddings, reciprocal rank fusion gitsync.py bare-repo backfill, push ingest, push.log, Gitea scan.py project discovery + location records discover*.py asset discovery, shared-code linking (core is shared with the remote agent) trust.py computed trust scores review.py targeted model review describe.py model-drafted project descriptions knowledge.py doc ingest, howto/asset seed server.py MCP tools, HTTP routes, JSON API cli.py serve | backfill | gitea | docs | seed | scan | embed | reindex | backup | sync | discover | review | trust | describe | purge web/ the single-file web UI (+ vendored marked.js) client/ hook, remote scan agent, slash command, per-OS installers systemd/ user-scope units: service, sync timer (6h), backup timer (02:45) docs/ user guide, architecture, git-commit-feed, clients, operations, publishing, python-vs-typescript server.json MCP Registry entry (PyPI package codemem-mcp) glama.json Glama listing maintainers Dockerfile container image: throwaway /data, no optional services
Storage: $CODEMEM_DB (default ~/.codemem/codemem.db, SQLite, WAL). Backups: $CODEMEM_BACKUP_DIR (default ~/.codemem/backups/).
Extracted from a system that has been running daily against 165 projects, 735 assets and 2,000+ commits across three machines. It is stable for that use, but it has had one operator, so expect rough edges the moment your layout differs from that one. Issues and pull requests welcome; please open an issue before a large change so we can agree on the shape. See CONTRIBUTING.md for how to run it locally and the two rules that are not negotiable, and SECURITY.md for what it stores and how to report a vulnerability.
Run scripts/smoke.sh before pushing: it boots the server against a throwaway database and checks that health, the web UI, the JSON API and the schema all come up.
Apache License 2.0. See LICENSE.
Copyright © 2026 Jeff Angelcyk.