What is the key difference between Graph Memory and Memora?

Graph Memory belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Memora belongs to the Knowledge & Memory category with local stdio execution.

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

Graph Memory operates under a Free / Open Source model (OAuth 2.0). Memora operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Graph Memory lists 6 tools with 1 views and 2 GitHub stars. Memora lists 6 tools with 2 views and 719 GitHub stars.

Can I use both Graph Memory and Memora 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

Graph Memory vs Memora

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

Graph Memory

Knowledge & Memory · Remote HTTP/SSE

Quality: 49/100 (Fair) | Auth: OAuth 2.0

Memora

Knowledge & Memory · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Verdict Summary: Choose Graph Memory if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Memora 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 Graph Memory when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Primary tools included: Typed entities and relationship graph, Local 384-dimensional embeddings with bge-small-en, Bi-temporal fact validity tracking.

Explore Graph Memory Details

Choose Memora when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEMORA_DB_PATH, MEMORA_STORAGE_URI, CLOUDFLARE_API_TOKEN, AWS_PROFILE, AWS_ENDPOINT_URL, MEMORA_CLOUD_ENCRYPT, MEMORA_ALLOW_ANY_TAG, MEMORA_GRAPH_PORT.

Feature & Specification Comparison

Specification	Graph Memory stevepridemore Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Personal knowledge graph for Claude on Neo4j. Typed entities (Person/Project/Decision/Preference/Concept), bi-temporal edge validity (validat/invalidat), per-type weighted decay, contradiction detection, and a nightly "dream" extraction process. Local bge-small-en embeddings, no API keys. Optional OAuth 2.1 + Cloudflare Tunnel for cross-device use across Claude Code, Desktop, web, and iOS.	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope

Tools & Capabilities Breakdown

Graph Memory Tools (6)

Typed entities and relationship graph

Local 384-dimensional embeddings with bge-small-en

Bi-temporal fact validity tracking

Per-type weighted decay

Contradiction detection and provenance

OAuth 2.1 support for remote access

Memora Tools (6)

Persistent storage with SQLite or cloud sync (S3, R2, D1)

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

Graph Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "stevepridemore-graph-memory": {
      "url": "https://your-host.example/mcp"
    }
  }
}

Memora Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-mcp-tools-memora": {
      "command": "npx",
      "args": [
        "-y",
        "wrangler"
      ],
      "env": {
        "MEMORA_DB_PATH": "YOUR_MEMORA_DB_PATH_HERE",
        "MEMORA_STORAGE_URI": "YOUR_MEMORA_STORAGE_URI_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
        "AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
        "AWS_ENDPOINT_URL": "YOUR_AWS_ENDPOINT_URL_HERE",
        "MEMORA_CLOUD_ENCRYPT": "YOUR_MEMORA_CLOUD_ENCRYPT_HERE",
        "MEMORA_ALLOW_ANY_TAG": "YOUR_MEMORA_ALLOW_ANY_TAG_HERE",
        "MEMORA_GRAPH_PORT": "YOUR_MEMORA_GRAPH_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

Graph Memory is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Memora belongs to Knowledge & Memory using local stdio subprocess. Select Graph Memory when you need capabilities focused on knowledge & memory and Memora when you require tools for knowledge & memory.

More alternatives to Graph Memory More alternatives to Memora Knowledge & Memory category hub Canonical compare URL