Memkin vs Krimto — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memkin vs Krimto
In-depth architectural comparison of the Memkin and Krimto 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: 56/100 (Good) | Auth: API Key required
Krimto
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memkin if you need specialized Knowledge & Memory tools running via a local process. Choose Krimto 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)).
Primary tools included: Feishu/Lark data collection, AI coding session ingestion, Local entity knowledge graph.
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
Open-source team memory layer for AI coding agents. Markdown files in git as storage, a user→team→org hierarchy as the access primitive, and one cross-vendor MCP server (Claude Code, Cursor, Codex, Gemini CLI). Hybrid SQLite + sqlite-vec retrieval. Apache-2.0.
Category & Scope
Tools & Capabilities Breakdown
Memkin Tools (6)
Feishu/Lark data collection
AI coding session ingestion
Local entity knowledge graph
Hybrid full-text and vector search
MCP read/write access
Obsidian bidirectional synchronization
Krimto Tools (6)
Markdown files stored in a user-controlled Git repository
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, Krimto belongs to Knowledge & Memory using local stdio subprocess. Select Memkin when you need capabilities focused on knowledge & memory and Krimto when you require tools for knowledge & memory.