Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
uvx claude-memory-manager==0.1.1O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add io.github.nyxtoolsdev-claude-memory-manager -- uvx claude-memory-manager==0.1.1Execute em um terminal.
{ "mcpServers": { "io.github.nyxtoolsdev-claude-memory-manager": { "command": "uvx", "args": [ "claude-memory-manager==0.1.1" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Cross-session memory for Claude Code — never lose context between sessions.
Claude Memory Manager automatically captures architectural decisions, code changes, bug fixes, and configuration choices from your Claude Code sessions, then intelligently retrieves relevant context when you start new sessions.
Cross-session memory for Claude Code — context capture, semantic search, recall
Every time you use Claude Code, valuable context is created and lost when the session ends:
Claude Memory Manager solves this by:
pip install claude-memory-manager
For local embeddings (no API key needed):
pip install claude-memory-manager[local]
For development:
pip install claude-memory-manager[dev]
claude-memory init
This creates the SQLite database at ~/.claude-memory/memory.db and saves a config file.
# Ingest all sessions from the default path (~/.claude/projects/)
claude-memory ingest
# Ingest from a specific path
claude-memory ingest /path/to/sessions
# Watch for new sessions and auto-ingest
claude-memory ingest --watch
# Search across all memories
claude-memory search "authentication setup"
# Filter by project
claude-memory search "database schema" --project /path/to/project
# Filter by category
claude-memory search "cors" --category config
# List all indexed projects
claude-memory context
# Generate summary for a specific project
claude-memory context /path/to/project
# With custom token limit
claude-memory context /path/to/project --max-tokens 3000
Add to your Claude Desktop config (see MCP Setup):
{
"mcpServers": {
"claude-memory": {
"command": "claude-memory-mcp",
"args": []
}
}
}
Memories are classified into these categories:
decision — Architectural and design decisionscode_change — Significant code modificationsbug_fix — Bug identification and resolutionconfig — Configuration and environment changeserror_resolution — Errors encountered and solvedpreference — User preferences and conventionsdiscussion — General discussion summariesFind your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the memory server:
{
"mcpServers": {
"claude-memory": {
"command": "claude-memory-mcp",
"args": []
}
}
}
See examples/claude-desktop-config.json for a complete example.
Once connected, Claude Desktop can use these tools:
claude-memory-manager/
src/claude_memory/
cli.py # Click CLI commands
mcp_server.py # MCP stdio server
config.py # Configuration management
core/
extractor.py # Memory extraction from conversations
embedder.py # Embedding generation + caching
indexer.py # Pipeline: parse -> extract -> embed -> store
retriever.py # Hybrid semantic + keyword search
summarizer.py # Context summary generation
parsers/
jsonl_parser.py # Claude Code session log parser
diff_parser.py # Unified diff parser
storage/
database.py # SQLite + FTS5 operations
models.py # Pydantic data models
migrations.py # Schema versioning
integrations/
anthropic_embeddings.py # Voyage AI API
local_embeddings.py # sentence-transformers
utils/
formatting.py # CLI output formatting
license.py # License validation
Session Logs (.jsonl)
|
[JSONL Parser] -----> ParsedSession
|
[Extractor] --------> Memory objects (categorized, scored)
|
[Embedder] ----------> Embeddings (bytes for SQLite BLOB)
|
[Indexer] -----------> SQLite DB (with FTS5 index)
|
[Retriever] ---------> Search results (hybrid ranked)
|
[Summarizer] --------> Context summary (markdown)
Configuration is loaded from (in priority order):
~/.claude-memory/config.json)If no provider is available, a stub provider is used (keyword search still works, but semantic search is disabled).
Where are my memories stored?
In a SQLite database at ~/.claude-memory/memory.db. All data stays local.
Does this send my code to any API?
Only if you configure the Voyage or Anthropic embedding provider. In that case, only memory text content (not full session logs) is sent to generate embeddings. Use local for fully offline operation.
How does deduplication work? Each memory's content is hashed (SHA-256). If a memory with the same hash already exists, it is skipped during ingestion.
How does hybrid search work? Results from cosine-similarity vector search (70% weight) are combined with SQLite FTS5 keyword search results (30% weight). Memories appearing in both get combined scores.
Can I export my memories?
Yes: claude-memory export > memories.json or claude-memory export -o file.json.
How do I prune old memories?
claude-memory prune --older-than 90d removes memories older than 90 days. Supports d (days), w (weeks), m (months), y (years).
# Clone and install in development mode
git clone https://github.com/nyxtools/claude-memory-manager.git
cd claude-memory-manager
pip install -e ".[dev]"
# Run tests
pytest
# Type check
mypy src/
# Lint
ruff check src/ tests/
MIT License. Copyright (c) 2026 NyxTools.
Cross-session memory for Claude Code — context capture, semantic search, recall
{ "mcpServers": { "io.github.nyxtoolsdev-claude-memory-manager": { "command": "uvx", "args": [ "claude-memory-manager==0.1.1" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Claude Memory Manager roda localmente via stdio.
Última verificação: 2026-11-09. Cross-session memory for Claude Code — context capture, semantic search, recall