claude-mem MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

Session-spanning memory via AI compression (not just grep of logs)
SQLite + Chroma vector search for semantic recall
Real-time web viewer at localhost:37777
<private> tags to exclude sensitive content from capture
Citation system — observations are referenced by ID in answers
Works with Claude Code, Gemini CLI, OpenCode; available via plugin marketplace

Demo en vivo

Cómo se ve en la práctica

claude-mem-skill.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-mem-skill": {
      "command": "npx",
      "args": [
        "claude-mem",
        "install"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-mem-skill": {
      "command": "npx",
      "args": [
        "claude-mem",
        "install"
      ]
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-mem-skill": {
      "command": "npx",
      "args": [
        "claude-mem",
        "install"
      ]
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-mem-skill": {
      "command": "npx",
      "args": [
        "claude-mem",
        "install"
      ]
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-mem-skill",
      "command": "npx",
      "args": [
        "claude-mem",
        "install"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-mem-skill": {
      "command": {
        "path": "npx",
        "args": [
          "claude-mem",
          "install"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add claude-mem-skill -- npx claude-mem install

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: claude-mem

Resume a multi-week project without re-briefing Claude every morning

👤 Engineers on long-running features or research ⏱ ~5 min beginner

Cuándo usarlo: You spend the first 10 minutes of every session re-explaining context that Claude had yesterday.

Requisitos previos

Claude Code installed — npm install -g @anthropic-ai/claude-code
claude-mem installed — npx claude-mem install (registers hooks in ~/.claude)

Flujo

Work normally

Just use Claude Code. claude-mem is passive — hooks capture events automatically.✓ Copiado

→ localhost:37777 shows the memory stream updating as you work
Start tomorrow's session

Where did we leave off on the migration branch?✓ Copiado

→ Claude recalls concrete facts + cites observation IDs
Correct misremembering

That's wrong about the DB schema — we decided to keep the v1 field. Mark that observation as corrected.✓ Copiado

→ mem-search writes a correction; future recall prioritizes it

Resultado: Sessions feel continuous. The re-briefing ritual disappears.

Errores comunes

Memory recalls stale facts after you change course — Explicitly mark corrections; mem-search respects recency and overrides
Sensitive code snippets get captured — Wrap them in <private>...</private> tags; hooks skip private blocks

Combinar con: filesystem

Turn individual sessions into team knowledge without writing docs

👤 Team leads; ICs who avoid writing postmortems ⏱ ~10 min intermediate

Cuándo usarlo: You solve a gnarly bug, explain the fix to Claude, and want that explanation findable next month without writing a README.

Flujo

Narrate your fix

Walk me through why the deadlock happened and the fix you just landed. Be complete — future me might read this.✓ Copiado

→ Claude writes a narrative; compression captures it
Tag the memory

Tag this observation with 'db-deadlock-2026-04' and 'billing-cluster'.✓ Copiado

→ Tags stored on the observation
Recall later

A month later: 'We've got another deadlock in billing — pull any prior notes.'✓ Copiado

→ The April note surfaces first

Resultado: Lightweight knowledge base that grows by itself.

Errores comunes

Memory gets noisy as months pass — Use mem-search --prune on low-signal old sessions; Endless Mode (beta) handles this automatically

Combinar con: memory

Keep customer data and secrets out of memory captures

👤 Anyone working with sensitive data ⏱ ~15 min intermediate

Cuándo usarlo: You work on code that touches PII or secrets and can't let them land in a local vector store.

Flujo

Wrap sensitive blocks

Write me the sample data with real test records wrapped in <private> tags so claude-mem doesn't capture the values.✓ Copiado

→ Private blocks are in the transcript but not in the memory store
Verify

Open localhost:37777 and check today's stream. Confirm no records from the <private> block appear.✓ Copiado

→ Private content absent
Add repo-wide policy

Update CLAUDE.md: 'Always wrap real customer data in <private>'.✓ Copiado

→ CLAUDE.md updated; future sessions inherit

Resultado: Memory is useful without being a data-leak surface.

Errores comunes

Forgetting to tag sensitive content — Make it a pre-commit / hook convention; claude-mem can enforce prompts that remind on detection

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

claude-mem-skill + filesystem

Memory recalls the file you edited, filesystem re-reads it

Pull from mem-search the last file we edited in the billing refactor; then read it and continue where we left off.✓ Copiado

claude-mem-skill + serena

Memory supplies the intent; Serena supplies the current code state

Memory says we're renaming ChargeService → BillingService; use Serena to finish the rename.✓ Copiado

claude-mem-skill + github

Cross-reference memory with real PR state

Memory says we opened a PR yesterday; use GitHub MCP to get its current status and review comments.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
mem-search (skill)	query: str, limit?: int, since?: date	Any time you'd ask Claude to 'remember' — full-text and semantic search over your history	free (local SQLite + embedding model)
mem-compress (hook)	session transcript	Automatic — runs at session end; rarely invoked manually	small Claude call per session
web viewer	URL http://localhost:37777	Debug what's being captured; check privacy filters	free

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Local SQLite + Chroma vectors; embedding model bundled
Tokens por llamada: Small — observations are already compressed
Monetario: Free (MIT)
Consejo: Compression calls use your Claude API key; set a monthly budget in the claude-mem config if you chat a lot

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: None for the tool itself; compression uses your existing Claude API key

Salida de datos: Compression calls go to Anthropic (your account); nothing else leaves your machine

No conceder nunca: Uploading the SQLite/Chroma store off-device without review — it contains transcripts

The local memory database is plaintext by default. If your disk isn't encrypted, enable FileVault/LUKS/BitLocker before using on sensitive projects.
Sharing your dotfiles or home dir via backup tools can leak memory. Add ~/.claude/mem/** to your backup exclusions if relevant.

Resolución de problemas

Errores comunes y soluciones

Web viewer at localhost:37777 won't load

Check the hook is running: ps aux | grep claude-mem. Reinstall with npx claude-mem install if it's absent.

Verificar: curl -I http://localhost:37777

Recall returns nothing useful

First few sessions are cold; memory gets better after ~10 sessions as patterns emerge. Also check that hooks are actually firing (see viewer).

Verificar: Open viewer during a session; events should stream in real time

Compression calls are expensive

Lower compression depth in config or use Endless Mode (beta) which is cheaper per session

Verificar: Check Anthropic usage dashboard for attribution

<private> content still shows up

Tag must be on its own lines; inline <private>…</private> in the middle of a sentence isn't parsed. Use block form.

Verificar: Reproduce and inspect the stored observation in the viewer

Alternativas

claude-mem vs otros

Alternativa	Cuándo usarla	Contrapartida
Memory MCP	You want explicit, user-controlled memory writes — not passive capture	You do the memory-saving yourself; less ambient, less magic
Serena memory	Your use case is code-focused and you'd rather have per-project notes than transcript compression	No session-stream capture; more project-level
Just take notes	You prefer explicit, human-curated notes	No automation; discipline-dependent

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills