Claude Memory Manager vs Memory MCP

In-depth architectural comparison of the Claude Memory Manager and Memory 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 Claude Memory Manager 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: memory_search, memory_recall, memory_save.

Explore Claude Memory Manager Details

M

Choose Memory MCP 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: memory_search, memory_related, memory_ask.

Explore Memory MCP Details

Feature & Specification Comparison

Specification	Claude Memory Manager Knowledge & Memory	M Memory MCP Knowledge & Memory
Summary	Cross-session memory for Claude Code — context capture, semantic search, recall	Persistent memory + git snapshots for Claude Code. Never lose context or code.
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "claude-memory-manager": {
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

{
  "mcpServers": {
    "memory-mcp-3": {
      "command": "npx",
      "args": [
        "-y",
        "memory-mcp-3"
      ]
    }
  }
}

Related MCP Server Comparisons