Engrava
MindQL queries, hybrid search, and a thought graph - read/write memory for AI agents.
The Model Context Protocol server for Engrava — expose an agent memory database to any MCP client (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, …) over stdio.
engrava-mcp is a standalone, runnable package that consumes Engrava's public
API. It is the one way to run Engrava as a memory server; the engrava library
itself ships no MCP code.
uv tool install engrava-mcp # recommended for daily use: a persistent install
engrava-mcp # spawned by your MCP client over stdio
uvx engrava-mcp runs it without an install step, and pip install engrava-mcp
works too. uvx keeps its environment in a cache. When that cache is cold, the
first start waits for the download; see Optional providers
for the [local] extra, where the download is largest.
Installing engrava-mcp pulls in engrava transitively, so you also get the
import engrava library in the same environment.
Compatibility
engrava-mcp follows Engrava's version: engrava-mcp X.Y.z targets engrava X.Y
and requires engrava >=X.Y,<X.(Y+1). This is a one-way version mirror for legibility —
not a lockstep: Engrava releases on its own cadence, and engrava-mcp patch releases
are independent.
| engrava-mcp | Works with engrava |
|---|---|
0.5.x |
>=0.5,<0.6 |
0.6.x |
>=0.6,<0.7 |
0.7.x |
>=0.7,<0.8 |
The dependency range is the source of truth. Normal installs resolve a compatible
engrava automatically; if you pin engrava yourself, keep it within that range. If no
matching engrava-mcp exists yet for an engrava newer than the table's last row, that
pairing is not yet verified/supported — not broken; stay on a supported pair until a
matching engrava-mcp ships.
Which package do I want?
| Goal | Install |
|---|---|
| Build on the Engrava Python API (memory DB in your own code) | pip install engrava |
| Run Engrava as a memory server for an MCP client | uvx engrava-mcp (or pip install engrava-mcp) |
There is no third option.
Migrating from engrava[mcp]
The server used to ship inside Engrava as the engrava[mcp] extra and an
in-engrava engrava-mcp command. As of Engrava 0.5.0 it lives here instead.
| Before | After |
|---|---|
pip install "engrava[mcp]" |
pip install engrava-mcp (or uvx engrava-mcp) |
engrava-mcp (installed by engrava) |
engrava-mcp (installed by this package) |
client mcp.json: "command": "engrava-mcp" |
client mcp.json: "command": "uvx", "args": ["engrava-mcp"] |
- Watch out:
pip install "engrava[mcp]"against Engrava 0.5 does not fail — pip ignores the now-unknown extra and quietly installs bareengrava, so it can look like the server installed when it did not. Installengrava-mcpinstead. - Update any pinned requirement strings (
engrava[mcp]>=...) to depend onengrava-mcp, not just reinstall. - Your store configuration is unchanged — the same
engrava.yaml/ env vars work exactly as before (see Configuration).
Configuration
The server resolves its store from environment variables, in priority order:
From the project's README.