Piia Engram runs on your own machine — the client starts it, so there is no endpoint to ping. 1 679 installs a week from pypi. Last commit 1 Sep 2026.
Local-first AI identity for MCP coding tools. Lessons, decisions, and context you control.
We read the source, 21 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"rm -rf",
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
_is_ephemeral = os.path.isfile("/.dockerenv") or _env_flag_enabled("ENGRAM_EPHEMERAL")
proc = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Piia Engram and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add piia-engram -- uvx piia-engram
{
"mcpServers": {
"piia-engram": {
"args": [
"piia-engram"
],
"command": "uvx"
}
}
}
[mcp_servers.piia-engram]
command = "uvx"
args = ["piia-engram"]
{
"mcpServers": {
"piia-engram": {
"args": [
"piia-engram"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"piia-engram": {
"args": [
"piia-engram"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
ENGRAM_MCP_STARTUP_SYNC (Skip optional local startup reconciliation during marketplace/client validation; set to background for local cross-tool sync.), ENGRAM_TOOLS (Expose the context-budget friendly default surface; set to all for the full advanced surface.), PYTHONIOENCODING (Force UTF-8 stdio frames on Windows-style consoles.).
The author declared them in the registry entry; get the values from the project itself.
Local-first AI context and memory server for cross-tool coding continuity.
Local-first memory for coding agents; stores decisions, bugs, and context across sessions.
Local-first memory and session continuity for AI coding agents over MCP. No cloud, no telemetry.
Persistent memory, coordination, and learning for AI agents. Local-first, 25 MCP tools.
Behavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT.
Local-first cycle coach MCP for phase-aware nutrition and training context.
MCP server for Obsidian vaults - AI tools with consistent canonical context. Local-first.
Real-time semantic security for AI coding agents and MCP tools
Answers built from our own checks of this server.