Cognee vs Memkin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cognee vs Memkin
In-depth architectural comparison of the Cognee 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
Cognee
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Memkin
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cognee 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 Cognee 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: LLM_API_KEY.
Primary tools included: Persistent and session-scoped memory, Graph, vector, and code-aware retrieval, Text and code ingestion.
Memory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources
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
Cognee Tools (6)
Persistent and session-scoped memory
Graph, vector, and code-aware retrieval
Text and code ingestion
Automatic search-strategy routing
Custom data models and ontologies
Memory improvement and deletion operations
Memkin Tools (6)
Feishu/Lark data collection
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).
Cognee is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memkin belongs to Knowledge & Memory using local stdio subprocess. Select Cognee when you need capabilities focused on knowledge & memory and Memkin when you require tools for knowledge & memory.