Context Mem vs Shodh Memory

In-depth architectural comparison of the Context Mem and Shodh Memory 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 Context Mem 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: observe, recall, search.

Explore Context Mem Details

Choose Shodh Memory 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: remember, recall, recall_by_tags.

Explore Shodh Memory Details

Feature & Specification Comparison

Specification	Context Mem Knowledge & Memory	Shodh Memory varun29ankuS Knowledge & Memory
Summary	Persistent memory for AI agents — 98%+ retrieval recall, 99% token savings, 44 tools	Cognitive memory for AI agents with Hebbian learning, 3-tier architecture, and knowledge graphs. Single 15MB binary, runs offline on edge devices.
Category & Scope	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": {
    "context-mem": {
      "command": "npx",
      "args": [
        "-y",
        "context-mem"
      ]
    }
  }
}

{
  "mcpServers": {
    "varun29ankus-shodh-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@shodh/memory-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons