What is the key difference between Marrow and Repomemory?

Marrow belongs to the Knowledge & Memory category with local stdio execution, while Repomemory belongs to the Knowledge & Memory category with local stdio execution.

How do I install Marrow or Repomemory in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Marrow and Repomemory free or paid?

Marrow operates under a Free / Open Source model (No auth required). Repomemory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Marrow lists 0 tools with 0 views and 0 GitHub stars. Repomemory lists 0 tools with 0 views and 2 GitHub stars.

Can I use both Marrow and Repomemory together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Marrow or Repomemory in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Marrow and Repomemory free to use, or do they require API keys?

Marrow is listed under a Free / Open Source model with No auth required . Repomemory operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Marrow and Repomemory at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both marrow-2 and repomemory as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Marrow has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Repomemory holds a Quality Score of 37 /100 ( Fair ) with 0 views, 0 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Marrow vs Repomemory

In-depth architectural comparison of the Marrow 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.

At a Glance & Executive Verdict

Marrow

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Repomemory

Knowledge & Memory · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Marrow if you need specialized Knowledge & Memory tools running via a local process. Choose Repomemory if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Marrow 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 Marrow 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	M Marrow Knowledge & Memory	R Repomemory Knowledge & Memory
Summary	Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.	Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Marrow Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Repomemory Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Marrow Configuration

mcpServers (Claude Desktop / Cursor)

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

Repomemory Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Marrow is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Repomemory belongs to Knowledge & Memory using local stdio subprocess. Select Marrow when you need capabilities focused on knowledge & memory and Repomemory when you require tools for knowledge & memory.

More alternatives to Marrow More alternatives to Repomemory Knowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Marrow

Popular comparisons with Repomemory

Repomemory vs Moxie Docs MCP