Memkin vs Context Keeper — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memkin vs Context Keeper
In-depth architectural comparison of the Memkin and Context Keeper 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
Context Keeper
Knowledge & Memory · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memkin if you need specialized Knowledge & Memory tools running via a local process. Choose Context Keeper if your workspace requires Knowledge & Memory integration with remote web transport. 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)).
Primary tools included: Feishu/Lark data collection, AI coding session ingestion, Local entity knowledge graph.
Memkin is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Context Keeper belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Memkin when you need capabilities focused on knowledge & memory and Context Keeper when you require tools for knowledge & memory.
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
LLM-driven context and memory management with wide-recall + precise-reranking RAG architecture. Features multi-dimensional retrieval (vector/timeline/knowledge graph), short/long-term memory, and complete MCP support (HTTP/WebSocket/SSE).