Mengram vs Memkin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mengram vs Memkin
In-depth architectural comparison of the Mengram and Memkin 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
Mengram
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Memkin
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Mengram if you need specialized Knowledge & Memory tools running via a local process. Choose Memkin 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 Mengram when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: MENGRAM_API_KEY.
Primary tools included: Semantic, episodic, and procedural memory types, Procedures evolve from failure feedback, Native multilingual retrieval (23 languages).
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.
Human-like memory layer for AI agents with semantic, episodic, and procedural memory. Claude Code hooks (auto-save, auto-recall, cognitive profile). 29 MCP tools, knowledge graph, smart triggers, multi-user isolation. Python & JS SDKs.
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
Category & Scope
Tools & Capabilities Breakdown
Mengram Tools (6)
Semantic, episodic, and procedural memory types
Procedures evolve from failure feedback
Native multilingual retrieval (23 languages)
Knowledge graph and smart triggers
Claude Code hooks for auto-save, auto-recall, and session persistence
Multi-user data isolation
Memkin 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).
Mengram is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memkin belongs to Knowledge & Memory using local stdio subprocess. Select Mengram when you need capabilities focused on knowledge & memory and Memkin when you require tools for knowledge & memory.