What is the key difference between M3 Memory and Reverie?

M3 Memory belongs to the Knowledge & Memory category with local stdio execution, while Reverie belongs to the Knowledge & Memory category with local stdio execution.

How do I install M3 Memory or Reverie 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 M3 Memory and Reverie free or paid?

M3 Memory operates under a Free / Open Source model (No auth required). Reverie operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

M3 Memory lists 0 tools with 0 views and 23 GitHub stars. Reverie lists 0 tools with 0 views and 69 GitHub stars.

Can I use both M3 Memory and Reverie 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.

Side-by-Side Model Context Protocol Comparison

M3 Memory vs Reverie

In-depth architectural comparison of the M3 Memory and Reverie 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

M3 Memory

Knowledge & Memory · Local stdio

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

Reverie

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose M3 Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Reverie 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 M3 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 M3 Memory Details

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

Feature & Specification Comparison

Specification	M M3 Memory Knowledge & Memory	R Reverie Knowledge & Memory
Summary	Local-first agentic memory — 100+ tools, 92% LongMemEval-S, hybrid search, GDPR, zero cloud.	Graph memory that dreams: Neo4j knowledge-graph memory for AI agents with hybrid search
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

M3 Memory Tools (0)

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

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

M3 Memory Configuration

mcpServers (Claude Desktop / Cursor)

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

Reverie Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "reverie": {
      "command": "npx",
      "args": [
        "-y",
        "@knowall-ai/mcp-neo4j-agent-memory"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to M3 Memory More alternatives to Reverie Knowledge & Memory category hub