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?

Memkin logo

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.
Projectmem logo

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

Specification
Memkin logo
Memkin
AndreLYL
Knowledge & Memory
Projectmem logo
Projectmem
riponcm
Knowledge & Memory
SummaryLocal-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 memkinLocal-first memory and judgment layer for AI coding agents. Captures issues, failed attempts, fixes, and decisions in readable Markdown + JSONL, re-injects them into future sessions, and warns at git commit before you repeat a mistake. 14 tools, works with Claude, Cursor, Antigravity, and Codex.
Category & ScopeKnowledge & MemoryKnowledge & Memory
Quality signal48/100 (Fair)49/100 (Fair)
Transport ProtocolLocal Subprocess (stdio)Local Subprocess (stdio)
Auth RequirementAPI Key requiredNo auth required
Pricing ModelBYOK (Pay Provider Direct)Free / Open Source
Required Env Vars
OPENAI_API_KEYOLLAMA_API_KEY
None required
Compatible Clients
Claude DesktopCursorWindsurfClineVS Code
Claude DesktopCursorWindsurfClineVS Code
Install path signalnpx · highnpx · low
Engagement & Health 3 views 0 copies 0 upvotes 5 stars 2 views 0 copies 0 upvotes 538 stars
Verified / OfficialCommunity ListingCommunity Listing
Open full listingView Memkin ListingView Projectmem Listing

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
mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "andrelyl-memkin": {
      "command": "npx",
      "args": [
        "-y",
        "memkin"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY_HERE"
      }
    }
  }
}
Projectmem Configuration
mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "riponcm-projectmem": {
      "command": "npx",
      "args": [
        "-y",
        "riponcm-projectmem"
      ]
    }
  }
}

Frequently Asked Questions

Memkin is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Projectmem belongs to Knowledge & Memory using local stdio subprocess. Select Memkin when you need capabilities focused on knowledge & memory and Projectmem when you require tools for knowledge & memory.

More alternatives to MemkinMore alternatives to ProjectmemKnowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Memkin

Popular comparisons with Projectmem