{"slug": "engrava-0-5-0-a-first-class-mcp-server", "title": "Engrava 0.5.0: a first-class MCP server", "summary": "Engrava 0.5.0 splits its MCP server into a standalone package, engrava-mcp, decoupling it from the core library. The server is now listed in the official MCP Registry as ai.sovantica/engrava, and the library adds new retrieval and audit features.", "body_md": "Engrava 0.5.0 pulls the MCP server out of the library.\n\nInstall `engrava`\n\nnow and you get the memory library and nothing else. The server ships separately, as `engrava-mcp`\n\n. The two were never really the same kind of thing — one is a dependency you import, the other is a process your MCP client spawns — and keeping them in one package meant everyone who installed the library also pulled in the server's dependencies, whether or not they ran a server. Splitting them gives each a clean install surface.\n\nIf you build directly on the Python API, nothing about your install changes:\n\n```\npip install engrava\n```\n\nIf you want Engrava as a memory server for an MCP client, reach for the standalone package instead:\n\n```\nuvx engrava-mcp\n# or\npip install engrava-mcp\n```\n\n`engrava-mcp`\n\nis a native stdio Model Context Protocol server that sits in front of an Engrava store. It exposes read tools, optional write tools, `engrava://`\n\nresources, and guided prompts to any MCP client that speaks stdio.\n\nIt's also listed in the official MCP Registry as `ai.sovantica/engrava`\n\n— PyPI package `engrava-mcp`\n\n, stdio transport — so a client that reads the registry can find it without you wiring anything by hand.\n\nOne detail that looks like a mismatch and isn't: the library is `engrava`\n\n0.5.0, but the server you install is `engrava-mcp`\n\n0.5.1. The two version independently. `engrava-mcp`\n\nfollows Engrava's minor line rather than its patch releases — every 0.5.x build targets `engrava>=0.5,<0.6`\n\n— so it moves on its own patch schedule underneath. Today that lands at 0.5.1.\n\nIn 0.4 the server rode along inside `engrava`\n\nas the `engrava[mcp]`\n\nextra. In 0.5 it graduates to a package of its own:\n\n| Before | After |\n|---|---|\n`pip install \"engrava[mcp]\"` |\n`pip install engrava-mcp` or `uvx engrava-mcp`\n|\n`engrava-mcp` installed by `engrava`\n|\n`engrava-mcp` installed by the standalone package |\nMCP client command: `engrava-mcp`\n|\nMCP client command: `uvx` , args: `[\"engrava-mcp\"]`\n|\n\nThis only breaks you if you were running Engrava as an MCP server. A plain `pip install engrava`\n\nlibrary upgrade is untouched, and the server still reads the same `engrava.yaml`\n\nor database path it always did — what moves is the install command and the launch command your client uses.\n\nThe packaging is the visible change, but the library moved too, mostly around retrieval and the audit path:\n\n`store.verify_journal()`\n\n, or from a shell with `engrava --db engrava.db verify`\n\n.`session_id`\n\nand `actor_id`\n\n.There's also a set of opt-in lifecycle features you can switch on and evaluate against your own workload: consolidation activation, deterministic memory hygiene, and caller-side whole-turn assembly. They ship in 0.5.0, off by default; whether they earn a place in your setup is yours to judge.\n\n`engrava`\n\nis the library, `engrava-mcp`\n\nis the server — install whichever you need:\n\n```\npip install engrava\nuvx engrava-mcp\n```\n\nCode and server docs:", "url": "https://wpnews.pro/news/engrava-0-5-0-a-first-class-mcp-server", "canonical_source": "https://dev.to/sovantica/engrava-050-a-first-class-mcp-server-2djc", "published_at": "2026-08-22 20:36:42+00:00", "updated_at": "2026-08-22 20:43:17.761434+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-infrastructure"], "entities": ["Engrava", "MCP", "PyPI", "MCP Registry"], "alternates": {"html": "https://wpnews.pro/news/engrava-0-5-0-a-first-class-mcp-server", "markdown": "https://wpnews.pro/news/engrava-0-5-0-a-first-class-mcp-server.md", "text": "https://wpnews.pro/news/engrava-0-5-0-a-first-class-mcp-server.txt", "jsonld": "https://wpnews.pro/news/engrava-0-5-0-a-first-class-mcp-server.jsonld"}}