What is the key difference between MCP Curiosity Engine and Memora?

MCP Curiosity Engine belongs to the Knowledge & Memory category with local stdio execution, while Memora belongs to the Knowledge & Memory category with local stdio execution.

How do I install MCP Curiosity Engine 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 MCP Curiosity Engine and Memora free or paid?

MCP Curiosity Engine operates under a Free / Open Source model (No auth required). Memora operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

MCP Curiosity Engine lists 5 tools with 0 views and 0 GitHub stars. Memora lists 6 tools with 2 views and 719 GitHub stars.

Can I use both MCP Curiosity Engine 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

MCP Curiosity Engine vs Memora

In-depth architectural comparison of the MCP Curiosity Engine 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

MCP Curiosity Engine

Knowledge & Memory · Local stdio

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

Memora

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose MCP Curiosity Engine if you need specialized Knowledge & Memory tools running via a local process. 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 MCP Curiosity Engine 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).
Primary tools included: find_dormant_notes, find_orphan_notes, suggest_replay_cycle.

Explore MCP Curiosity Engine 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.
Primary tools included: Persistent storage with SQLite or cloud sync (S3, R2, D1), Hierarchical memory organization with sections and subsections, Semantic search using TF-IDF, sentence-transformers, and OpenAI embeddings.

Feature & Specification Comparison

Specification	M MCP Curiosity Engine Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Surface the notes you forgot you wrote — DMN replay for markdown vaults.	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

MCP Curiosity Engine Tools (5)

find_dormant_notes

List notes that are structurally dormant — low incoming wikilink count AND old mtime. These are the notes most at risk of being forgotten.

find_orphan_notes

List notes with zero incoming wikilinks — structurally isolated, the extreme case of dormancy.

suggest_replay_cycle

Run the full DMN-inspired replay cycle: sample dormant notes with bias (40% random / 30% least-linked / 30% orphans), extract their concepts, generate cross-domain bridge queries between them, return notes to revisit. The core moat.

find_cross_domain_bridges

Surface pairs of notes from DIFFERENT top-level directories that share concepts. These are the surprise connections — ideas that span your vault's silos.

random_deep_cut

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

MCP Curiosity Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-curiosity-engine": {
      "command": "uvx",
      "args": [
        "mcp-curiosity-engine"
      ]
    }
  }
}

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

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

More alternatives to MCP Curiosity Engine More alternatives to Memora Knowledge & Memory category hub Canonical compare URL