MCP Local Rag vs Code Memory

In-depth architectural comparison of the MCP Local Rag and Code 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 MCP Local Rag 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).

Explore MCP Local Rag Details

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

Explore Code Memory Details

Feature & Specification Comparison

Specification	MCP Local Rag Knowledge & Memory	Code Memory Knowledge & Memory
Summary	Semantic code & doc search with keyword boost. AST parsing, local embeddings, privacy-first.	Local semantic code search with Git history. Works offline, no API key needed.
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": {
    "mcp-local-rag": {
      "command": "npx",
      "args": [
        "-y",
        "@damoqiongqiu/mcp-local-rag"
      ]
    }
  }
}

{
  "mcpServers": {
    "code-memory": {
      "command": "uvx",
      "args": [
        "code-memory"
      ]
    }
  }
}

Related MCP Server Comparisons