In-depth architectural comparison of the Rms Memory Mcp 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
Rms Memory Mcp
Knowledge & Memory · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
Memkin
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Rms Memory Mcp if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. 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 Rms Memory Mcp when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Local-first persistent memory for AI coding agents. Hybrid vector + full-text search (LanceDB + Tantivy), separate Markdown and Tree-sitter code indexes, per-project isolated vaults shared across IDEs (Cursor, Zed, Claude Code, Codex), bounded recall with abstain-on-low-confidence.
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
Rms Memory Mcp Tools (6)
Project-isolated centralized Markdown vaults
Hybrid LanceDB vector and Tantivy full-text retrieval
Optional Tree-sitter code indexing with dirty-path watch mode
Bounded recall with confidence thresholds and abstention
Session checkpoints, project overviews, and bootstrap instructions
Cross-project federated search with Reciprocal Rank Fusion
Memkin Tools (6)
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).
Rms Memory Mcp is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Memkin belongs to Knowledge & Memory using local stdio subprocess. Select Rms Memory Mcp when you need capabilities focused on knowledge & memory and Memkin when you require tools for knowledge & memory.