Engrava 0.5.0 splits memory library and MCP server into separate packages
The Engrava project has released version 0.5.0, separating its memory library and MCP server into two distinct packages: engrava and engrava-mcp. Previously bundled together as an optional extra, the split ensures users only install the dependencies relevant to their use case. The standalone engrava-mcp package is a native stdio Model Context Protocol server and is now listed in the official MCP Registry for easier discovery by compatible clients. Alongside the packaging change, version 0.5.0 also introduces scoped ranked retrieval with metadata filters, audit verification via hash-chain journal, and typed provenance capture. Users who ran Engrava as an MCP server will need to update their install and launch commands, while those using only the Python library are unaffected.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in