In-depth architectural comparison of the Engram and Plur MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Engram
Knowledge & Memory · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Plur
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Engram if you need specialized Knowledge & Memory tools running via a local process. Choose Plur if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Engram when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret detection, and contradiction handling. 6 MCP tools (remember, recall, forget, feedback, context, status) over stdio. Zero cloud, no API keys, fully offline. Works with Claude Desktop/Code, Cursor, and Windsurf. npm install -g @hbarefoot/engram
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP.
Engram is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Plur belongs to Knowledge & Memory using local stdio subprocess. Select Engram when you need capabilities focused on knowledge & memory and Plur when you require tools for knowledge & memory.