Projectmem vs Threadctx MCP

In-depth architectural comparison of the Projectmem and Threadctx MCP 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.

Which MCP Server Should You Choose?

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.

Explore Projectmem Details

Choose Threadctx MCP when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• You have access to required keys: THREADCTX_API_KEY, THREADCTX_MODE, THREADCTX_NO_AUTO_RULES.
• Primary tools included: .

Feature & Specification Comparison

Specification	Projectmem riponcm Knowledge & Memory	Threadctx MCP threadctx-dev Knowledge & Memory
Summary	Local-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.	Shared team memory for AI coding agents. Decisions, fixes, and gotchas persist per repo and are shared across Claude Code, Cursor, and any MCP client — what one teammate's agent learns, everyone's agents remember. Local-first, zero-dependency. npx -y threadctx-mcp
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "riponcm-projectmem": {
      "command": "uvx",
      "args": [
        "projectmem"
      ]
    }
  }
}

{
  "mcpServers": {
    "threadctx-dev-threadctx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "threadctx-mcp"
      ],
      "env": {
        "THREADCTX_API_KEY": "YOUR_THREADCTX_API_KEY_HERE",
        "THREADCTX_MODE": "YOUR_THREADCTX_MODE_HERE",
        "THREADCTX_NO_AUTO_RULES": "YOUR_THREADCTX_NO_AUTO_RULES_HERE"
      }
    }
  }
}

Related MCP Server Comparisons