RAWThink vs Repomemory

In-depth architectural comparison of the RAWThink and Repomemory 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?

R

Choose RAWThink 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 RAWThink Details

Choose Repomemory 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 Repomemory Details

Feature & Specification Comparison

Specification	R RAWThink Knowledge & Memory	Repomemory Knowledge & Memory
Summary	Persistent memory for AI thinking partnerships: hybrid search and a temporal knowledge graph.	Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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": {
    "rawthink": {
      "command": "npx",
      "args": [
        "-y",
        "rawthink"
      ]
    }
  }
}

{
  "mcpServers": {
    "repomemory": {
      "command": "npx",
      "args": [
        "-y",
        "repomemory"
      ]
    }
  }
}

Related MCP Server Comparisons