Most MCP memory servers are either simple key-value stores or plain text search wrappers.
Memory Engine is different: it models memory as typed atoms connected by typed bonds, then retrieves context with a hybrid ranking pipeline that combines:
full-text search (SQLite FTS5)
Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
Clave de API
MEMORY_DB_PATH, MARKDOWN_SOURCE, MEMORY_PORT
Última comprobación
2026-11-09
Estrellas
—
Herramientas
—
Disponibilidad
—
semantic similarity via local Ollama embeddings
confidence, recency, and weight
graph expansion from related memories
The goal is not just storage. The goal is a memory system that can recall, connect, decay, curate, and learn over time.
Highlights
Local-first — SQLite database, optional local embeddings via Ollama, no required cloud API.
MCP-native — exposes 35 tools through FastMCP.
Graph-aware recall — expands top hits through bidirectional bonds for richer context.
Semantic search — meaning-based retrieval with nomic-embed-text.
Markdown coexistence — import existing notes one-way without replacing your human-readable memory.
Error memory — remembers mistakes and corrections, with auto-promotion to preferences after repeated failures.
Cognitive curator — non-destructive maintenance pass for compaction, bond suggestions, duplicate detection, and isolated atom classification.
remember(
title="Use PostgreSQL for analytics",
body="SQLite is kept for local memory, PostgreSQL is used for multi-user analytics.",
type="decision",
domain="project:analytics",
confidence=0.9,
tags=["database", "architecture"]
)
recall(query="what database did we choose for analytics?", limit=5)
working_set(
query="continue the analytics backend work",
domain="project:analytics",
limit=8,
graph_depth=1
)
Security
By default, Memory Engine runs in open mode (no auth) — safe for stdio
or trusted local environments.
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Preguntas
¿Cómo instalo Memory Engine MCP?
Copia en esta página la configuración http para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
¿Memory Engine MCP necesita una clave de API?
El publicador indica estas variables de entorno: MEMORY_DB_PATH, MARKDOWN_SOURCE, MEMORY_PORT.
¿Qué transporte usa Memory Engine MCP?
Se accede a Memory Engine MCP por HTTP.
¿Cuándo se comprobó Memory Engine MCP por última vez?
Última comprobación: 2026-11-09. Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.