Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

codemem

de jeang42versión 0.1.0i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.jeang42/codemem

Instalar

Resumen

Descripción del creador (original en inglés)

Shared memory for coding agents: projects, reusable code, sessions and commits across machines

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: Streamable HTTP
  • Categoría: Búsqueda y memoria de IA

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: CODEMEM_DATA, CODEMEM_DB, CODEMEM_HOST, CODEMEM_PORT, OLLAMA_URL, CODEMEM_EMBED, GIT_ROOT

Necesitas

  • PyPIuv de Python instalado (para el comando uvx)

¿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 serve

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

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ú.

Abrir en VS Code

O copia la configuración 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.

Valores que debes completar

  • CODEMEM_DATA env
    Directory for the database and backups
  • CODEMEM_DB env
    Path to the SQLite database (overrides CODEMEM_DATA)
  • CODEMEM_HOST env
    Address to bind. The server has no authentication; use 127.0.0.1 unless the network is trusted
  • CODEMEM_PORT env
    Port for MCP (/mcp) and the web UI. The transport URL assumes 8055
  • OLLAMA_URL env
    Ollama base URL for embeddings (semantic search). Without it, search is BM25 only
  • CODEMEM_EMBED env
    Set to false to disable embeddings entirely
  • GIT_ROOT env
    Directory of bare git repos to read for the commit feed

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

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

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub jeang42, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Búsqueda y memoria de IAi

  • Más estrellas que el 0% de los otros 7247 servidores de esta categoría
  • Publicado en el registro más recientemente que el 48% de los otros 7247 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 7247 servidores de esta categoría

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.

Preguntas frecuentes

¿Es seguro codemem?

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.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

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).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro hace 42 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Context7, Codebase Memory, Exa

Alternativas

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

Context7

de upstash

Up-to-date docs for AI agents

Computadora o nube★ 64.224MITActualizado hoy
Instalar

Codebase Memory

de DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Se ejecuta en tu computadora★ 48.148MITActualizado hace 20 días
Instalar

Exa

de exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Se ejecuta en la nube★ 5213MITActualizado el mes pasado
Instalar

README del creador

Abrir el README

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.

codemem

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.

What makes it different

Inventory scripts snapshot a directory and you read the report once. Registries list what people published. codemem does neither.

  • Trust from evidence, not from stars. Every project and asset gets a computed score from how recently it changed, how much work went into it, whether it is actually deployed and running, whether anything else imports it, and whether a human vouched for it. 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.
  • It finds the copies you forgot. Discovery mines every repo at HEAD for scripts, modules, service units, Dockerfiles and MCP servers, hashes their functions, and links repos that share code. It will tell you that you wrote the same retry wrapper in three places.
  • Agents feed it automatically. A session hook records what each Claude Code session did, and gives the next session a brief on the project it just opened. The catalogue builds itself.
  • Maturity is a first-class label. 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.
  • Your code stays where it is. codemem stores metadata: names, descriptions, imports, symbols, function hashes, commit records. It does not copy your source anywhere.

Endpoints

EndpointWhat
http:// :8055/mcpMCP (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/healthliveness

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.

Requirements

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.

Why

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.

Install from PyPI

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.

Run with Docker

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:8055 publishes 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.

Quick start

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.

What Claude sees

ToolUse
searchhybrid BM25 + embedding search over everything. First call before building anything
project_briefeverything about one project, by name or working directory
list_projectsfilter by status, tag, machine, audience, visibility
update_projectdescription, purpose, status, tags, audience, origin (own/vendor), visibility, maturity
register_assetrecord a reusable script/module/prompt/skill/service with a one-line usage
find_assetssearch or list assets by kind/tag/project, or by imported library
log_sessionwhat was done, decided, used, abandoned, and what is next
add_notedecision, howto, resource, issue, idea
delete_noteremove a note written by mistake, with its index and embedding rows
link_itemsproject uses / could-reuse / supersedes / derived-from another
ratematurity: 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_handoffstrack one implementation replacing another through candidate, shadow, verified, promoted
howtohow to publish, add a machine, use codemem, plus whatever docs are ingested
activitycommits and sessions across all machines, last N days
add_scan_root / scan_pathregister a directory to scan; scan now (server machine)
statscounts, machines, index coverage
helpworkflow, tool list, label vocabularies. Also /codemem in Claude Code, /codemem searches

Where the data comes from

  • Git host: every bare repo in 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.
  • Gitea (optional): descriptions, topics and web URLs, via its API with a read token.
  • Local scan: project directories under registered roots, per machine. On the server this is automatic; other machines run client/codemem_agent.py once a root is registered.
  • Discovery: every own repo is mined at HEAD for scripts, modules, units, Dockerfiles, prompts and MCP servers, recorded as auto-discovered assets, with shared-code links between repos.
  • Docs: markdown from CODEMEM_DOC_SOURCES (this repo by default), re-hashed every sync.
  • Claude Code: session records from the hook, plus whatever Claude writes with the tools.
  • Local model (optional, via Ollama): embeddings for semantic search, drafted descriptions, and a targeted review of near-duplicate functions and thinly described code.

Layout

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/).

Status and contributing

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.

License

Apache License 2.0. See LICENSE.

Copyright © 2026 Jeff Angelcyk.

Pregunta a PopNx