Memkin vs Engram — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memkin vs Engram
In-depth architectural comparison of the Memkin 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
Memkin
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Engram
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Memkin 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 Memkin when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENAI_API_KEY, OLLAMA_API_KEY.
Primary tools included: Incremental and historical data collection from 7 Feishu sources, AI session data ingestion from Claude Code, Codex, Hermes/OpenClaw, Private local knowledge graph with entity linking and identity merging.
Local-first personal memory for AI agents. Ingests Feishu/Lark chats and Claude Code / Codex sessions, distills them into a private entity knowledge graph (people, projects, decisions, tasks), and serves it to any agent over MCP — read and write. npx memkin
Second brain your agents read and write, over a git-backed markdown vault. Authority-aware search ranks superseded and archived notes below live ones (from frontmatter, no vector DB), so agents quote the current doc, not the dead one. Per-agent read-only or write tokens, a git audit trail of every change with diffs, a knowledge-graph dashboard, and Obsidian compatibility.
Category & Scope
Tools & Capabilities Breakdown
Memkin Tools (6)
Incremental and historical data collection from 7 Feishu sources
AI session data ingestion from Claude Code, Codex, Hermes/OpenClaw
Private local knowledge graph with entity linking and identity merging
Hybrid retrieval combining full-text search and vector similarity
Privacy-preserving data handling with reversible and irreversible redaction
MCP server supporting stdio and Streamable HTTP transport
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).
Memkin is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram belongs to Knowledge & Memory using local stdio subprocess. Select Memkin when you need capabilities focused on knowledge & memory and Engram when you require tools for knowledge & memory.
Primary tools included: Git-backed markdown storage with no database dependency, Authority-aware search excluding superseded or expired notes, Per-agent read and write tokens for access control.