Sessionmem vs Engram — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sessionmem vs Engram
In-depth architectural comparison of the Sessionmem and Engram 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
Sessionmem
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Engram
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Sessionmem if you need specialized Knowledge & Memory tools running via a local process. Choose Engram 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 Sessionmem 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).
Primary tools included: Local SQLite storage of session memories, Automatic summary generation of key session points, Context injection at the start of new sessions.
Local-first memory layer for AI coding assistants. Watches your coding sessions and injects a compact summary at the start of each new session. No cloud, no account, just a SQLite file on your machine. Works with Claude Code, Cursor, Cline, Windsurf, and any other MCP host.
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
Category & Scope
Tools & Capabilities Breakdown
Sessionmem Tools (6)
Local SQLite storage of session memories
Automatic summary generation of key session points
Context injection at the start of new sessions
Secret redaction to scrub sensitive data before saving
Configurable retention policy for memory pruning
Compatible with multiple MCP hosts and AI tools
Engram Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Sessionmem is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram belongs to Knowledge & Memory using local stdio subprocess. Select Sessionmem when you need capabilities focused on knowledge & memory and Engram when you require tools for knowledge & memory.