Side-by-Side Model Context Protocol Comparison
Memkin vs Projectmem
In-depth architectural comparison of the Memkin and Projectmem 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: 48/100 (Fair) | Auth: API Key required
Projectmem
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Memkin if you need specialized Knowledge & Memory tools running via a local process. Choose Projectmem 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)).
- 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.
Choose Projectmem 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: Local-first memory stored in .projectmem directory, Typed event storage: issues, attempts, fixes, decisions, notes, Pre-commit git hook warnings for repeated mistakes.
Feature & Specification Comparison
Tools & Capabilities Breakdown
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
Projectmem Tools (6)
Local-first memory stored in .projectmem directory
Typed event storage: issues, attempts, fixes, decisions, notes
Pre-commit git hook warnings for repeated mistakes
Integration with Claude Code, Claude Desktop, Cursor, Antigravity, Codex
Global workspace dashboard aggregating multiple projects
Real-time file watcher and automatic git hook installation
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 Configuration
Projectmem Configuration