Side-by-Side Model Context Protocol Comparison
Agentkits Memory vs Memkin
In-depth architectural comparison of the Agentkits Memory 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Memkin
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Agentkits Memory 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 Agentkits Memory when:
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: 100% local SQLite database storage with no cloud or API keys, Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity, Automatic session tracking and context injection via hooks.
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.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Agentkits Memory Tools (6)
100% local SQLite database storage with no cloud or API keys
Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity
Automatic session tracking and context injection via hooks
Background workers for AI enrichment and data compression
Web viewer UI for browsing, searching, and editing memories
Cross-platform compatibility with multiple AI coding MCP clients
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
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).
Agentkits Memory Configuration
Memkin Configuration