Memory Engine MCP server
io.github.SimoneB79/memory-engine-mcp·v1.5.3·1 starsLocal-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
1 stars
Reviews
Write oneNobody has reviewed Memory Engine MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Memory Engine MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Memory Engine MCP compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 802 Databases servers
- GitHub stars
- 1
- more than 45% of 602 Databases servers
Install Memory Engine MCP in Claude Code, Cursor or VS Code
claude mcp add memory-engine-mcp -- docker run -i --rm ghcr.io/simoneb79/memory-engine-mcp:1.5.3
What the publisher says
From the Memory Engine MCP repository's README, as published. We do not edit it. Read it on GitHub
<!-- mcp-name: io.github.simoneb79/memory-engine-mcp -->
🧠 Memory Engine MCP
Local-first, graph-aware long-term memory for AI assistants. SQLite + semantic search + knowledge graph + MCP tools for agents that need continuity.
Works with Claude Desktop · Claude Code · Cursor · Cline · Windsurf · OpenClaw · any MCP client
Why Memory Engine?
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)
- 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.
- Session watcher — canonical OpenClaw SQLite ingestion (schema 17), reset-aware digests, and JSONL legacy fallback.
- Backup & restore — full SQLite snapshots, JSON export/import, verified restores with automatic safety backups.
- Auth & hardening — optional API token, secure bind, input validation, rate limiting.
- Test suite — 144 tests covering CRUD, ranking, migrations, auth, backup, concurrency, and transcript ingestion.
- Benchmark — CLI recall quality suite with Precision@K, MRR, latency percentiles.
Architecture
AI assistant / MCP client
│
▼
FastMCP server — 35 tools
│
▼
Memory engine — hybrid ranking, graph recall, decay, learning
│
├── SQLite — atoms, bonds, FTS5, JSON metadata, versions
├── Ollama — optional local embeddings
├── Curator — conservative maintenance
└── Session watcher — OpenClaw SQLite + JSONL fallbackMCP Tools
Memory
Knowledge graph
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Memory Engine MCP: common questions
- Is Memory Engine MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Memory Engine MCP safety report
- How do I install Memory Engine MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Memory Engine MCP need an API key?
- No secret keys are declared. It reads 3 settings from the environment.
- Is Memory Engine MCP maintained?
- The last commit was 41 days ago (2026-09-24). The latest release is v1.5.3.
- What can I use instead of Memory Engine MCP?
- Servers from other publishers that do the same job: Remem MCP server, ZenBrain Memory MCP server and open-memex MCP server.
- How does Memory Engine MCP compare with other Databases MCP servers?
- safety score 88/100 (higher than 75% of 802 Databases servers); github stars 1 (more than 45% of 602 Databases servers). Full comparison.
Alternatives to Memory Engine MCP
Same job from other publishers: the closest match first, then the best rated.
- RememLocal-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.not reviewedEstablishedB
- ZenBrain MemoryAgent memory: working, episodic, semantic, procedural and core layers. Local SQLite, no account.not reviewedGrowingA
- open-memexLocal-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.not reviewedGrowingB
- GraphmemShared local memory for coding agents: SQLite, semantic recall, linked entities, code navigation.not reviewedGrowingA
- SAME - Stateless Agent Memory EnginePersistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.not reviewedGrowingB