Agentkits Memory vs Engram — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agentkits Memory vs Engram
In-depth architectural comparison of the Agentkits Memory 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Engram
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agentkits Memory 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 Agentkits Memory 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: 100% local SQLite database storage with no cloud or API keys, Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity, Automatic session tracking and context injection via hooks.
Persistent memory for AI coding assistants with hybrid search (FTS5 + vector embeddings), session tracking, automatic context hooks, and web viewer. SQLite-based with no daemon process — works with Claude Code, Cursor, Windsurf, and any MCP client.
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
Agentkits Memory Tools (6)
100% local SQLite database storage with no cloud or API keys
Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity
Automatic session tracking and context injection via hooks
Background workers for AI enrichment and data compression
Web viewer UI for browsing, searching, and editing memories
Cross-platform compatibility with multiple AI coding MCP clients
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).
Agentkits Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram belongs to Knowledge & Memory using local stdio subprocess. Select Agentkits Memory when you need capabilities focused on knowledge & memory and Engram when you require tools for knowledge & memory.