What is the key difference between Memory OS AI and Reverie?

Memory OS AI 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 Memory OS AI 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 Memory OS AI and Reverie free or paid?

Memory OS AI 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?

Memory OS AI lists 0 tools with 0 views and 3 GitHub stars. Reverie lists 0 tools with 0 views and 69 GitHub stars.

Can I use both Memory OS AI 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

Memory OS AI vs Reverie

In-depth architectural comparison of the Memory OS AI 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

Memory OS AI

Knowledge & Memory · Local stdio

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

Reverie

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Memory OS AI 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 Memory OS AI 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 Memory OS AI 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 Memory OS AI Knowledge & Memory	R Reverie Knowledge & Memory
Summary	Adaptive memory for AI agents — FAISS search, chat extraction, cross-project linking	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

Memory OS AI 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).

Memory OS AI Configuration

mcpServers (Claude Desktop / Cursor)

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

Reverie Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Memory OS AI More alternatives to Reverie Knowledge & Memory category hub