ai.sovantica/engrava vs Memory Engine MCP
ai.sovantica/engrava is an MCP server published by sovantica.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Memory Engine MCP is an MCP server published by SimoneB79. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ai.sovantica/engrava |  Memory Engine MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Downloads/month (PyPI): 428 Downloads/week (PyPI): 54 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.5.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ai.sovantica/engrava | Memory Engine MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (engrava-mcp) | On your machine (ghcr.io/simoneb79/memory-engine-mcp:1.5.3) |
| Transport (differs) | stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 3, secrets among them: 0 | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/sovantica/engrava-mcp | github.com/simoneb79/memory-engine-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ai.sovantica/engrava
MindQL queries, hybrid search, and a thought graph - read/write memory for AI agents.
Memory Engine MCP
Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
How to run each
ai.sovantica/engrava As a local MCP server: PyPI package
claude mcp add --env "ENGRAVA_DB_PATH=<YOUR_ENGRAVA_DB_PATH>" --transport stdio engrava -- uvx engrava-mcpRequires: ENGRAVA_DB_PATH
Memory Engine MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only ai.sovantica/engrava asks for
ENGRAVA_DB_PATHENGRAVA_MCP_CONFIGENGRAVA_MCP_READ_ONLY
Only Memory Engine MCP asks for
MARKDOWN_SOURCEMEMORY_DB_PATHMEMORY_PORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: ai.sovantica/engrava · What it can do: Memory Engine MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.