Local Memory MCP Server
A local-first MCP server that gives AI agents shared, durable memory through hybrid semantic search, SQLite FTS5, and a knowledge graph—without Docker or a required cloud service.

Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
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
A local-first MCP server that gives AI agents shared, durable memory through hybrid semantic search, SQLite FTS5, and a knowledge graph—without Docker or a required cloud service.

A lightweight, powerful local memory server for AI agents supporting text, entities, and relations. Enables persistent codebase understanding and user preference management.
sqlite-vec is available, local
all-MiniLM-L6-v2 embeddings and FTS5 keyword evidence are merged. FTS
remains available as the explicit fallback.last week or
in 2025, or pass an explicit ISO startDate and endDate.OLLAMA_URL you configure.For every option and tool, see the extended guide.
better-sqlite3 has no matching prebuild.Windows ARM64 semantic search is supported by a bundled, checksum-verified
sqlite-vec v0.1.9 DLL. WSL2 remains a supported alternative.
Add the published package to an MCP client:
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "@beledarian/mcp-local-memory@2"],
"env": {
"ARCHIVIST_STRATEGY": "nlp"
}
}
}
}
The default database is ~/.memory/memory.db. The first semantic recall may
download the local embedding model.
Global installation provides both memory and mcp-local-memory:
npm install -g @beledarian/mcp-local-memory@2
memory --help
From source:
git clone https://github.com/Beledarian/mcp-local-memory.git
cd mcp-local-memory
npm install
npm run build
npm start
See the Codex + WSL2 setup when the database or server runs inside Linux.
mcp-local-memory supports native HTTP/SSE transport for centralized setups across multiple workstations, laptops, Tailnets, or VPS instances:
# Run standalone SSE server on port 8320 with optional Bearer token auth:
node dist/index.js --transport sse --port 8320 --token "your-secret-token"
# Or run via Docker Compose:
docker compose up -d
Configure your remote MCP client (mcp_config.json):
{
"mcpServers": {
"memory": {
"url": "https://your-server.ts.net:8320/sse",
"headers": {
"Authorization": "Bearer your-secret-token"
}
}
}
}
All scoring, context, archivist, task, and extension variables are documented in the configuration reference.
recall supports both topical and temporal questions:
yesterday, last week, and in 2025 are
recognized in the query. ISO startDate and endDate filters are also
available.0.03 by default; it does not rewrite importance or refresh decay.reinforce_memory provides the stronger, durable feedback path:
used or important record positive evidence.irrelevant lowers importance.incorrect or outdated suppresses the memory without deleting history.restore returns a suppressed memory to active recall.The extended scoring guide documents the formula, thresholds, deduplication, privacy limits, decay, and every familiarity control.
Free-form memories and structured knowledge complement each other:
Project A --[uses]--> SQLite. Creating a relation also creates any missing
endpoint as an Unknown entity.ARCHIVIST_STRATEGY=nlp for local extraction, llm for the
configured Ollama endpoint, or passive for manual graph maintenance.Use recall for ranked free-form retrieval and read_graph when connections
between named concepts matter. They are complementary views of the same local
knowledge base.
See the complete tool reference for arguments and lifecycle behavior.
When upgrading from 1.x:
MEMORY_DB_PATH;MEMORY_SEMANTIC_WEIGHT now means relevance versus importance;The project does not claim crash-proof, zero-loss migration under every interruption scenario, so a verified backup remains the safety boundary.
Older releases passively increased importance and access_count during
recall. Preview normalization before changing anything:
npm run normalize:importance -- --db ~/.memory/memory.db
Applying normalization is optional and requires an explicit, non-existing backup path. See the migration and normalization guide.
These commands require a source checkout:
npm install
npm run build
npm test
npm test covers scoring, schema migration, lifecycle and familiarity,
privacy/provenance, MCP contracts, packaging, and native vector or FTS fallback.
MIT
A lightweight, powerful local memory server for AI agents supporting text, entities, and relations. Enables persistent codebase understanding and user preference management.
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.
MCP Local Memory roda localmente via stdio.
Última verificação: 2026-10-27. A lightweight, powerful local memory server for AI agents supporting text, entities, and relations. Enables persistent codebase understanding and user preference management.