What is the key difference between Engram MCP and Memora?

Engram MCP 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 Engram MCP 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 Engram MCP and Memora free or paid?

Engram MCP 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?

Engram MCP lists 11 tools with 2 views and 1 GitHub stars. Memora lists 6 tools with 2 views and 724 GitHub stars.

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

Engram MCP vs Memora

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

Engram MCP

Knowledge & Memory · Local stdio

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

Memora

Knowledge & Memory · Local stdio

Quality: 49/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Engram MCP 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 Engram MCP 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).
You have access to required keys: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
Primary tools included: remember, recall, search.

Explore Engram MCP 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	Engram MCP Cartisien Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope

Tools & Capabilities Breakdown

Engram MCP Tools (11)

remember

Store a new memory with automatic entity extraction, theme detection, and relationship mapping.

recall

Retrieve relevant memories with entity, theme, and emotional context. Returns 360° relational intelligence around the query.

Raw hybrid search with pagination and filtering. Use for precise control over results.

context

Get 360° context around a specific entity, theme, or memory. Returns timeline, relationships, emotional arc, and key memories.

impact

Analyze how a new piece of information would affect existing memory structure. Detects conflicts, affected entities, and themes before storing.

detect_changes

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

Engram MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cartisien-engram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cartisien/engram-mcp"
      ],
      "env": {
        "ENGRAM_DB": "YOUR_ENGRAM_DB_HERE",
        "ENGRAM_EMBEDDING_URL": "YOUR_ENGRAM_EMBEDDING_URL_HERE"
      }
    }
  }
}

Memora Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-mcp-tools-memora": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-mcp-tools-memora"
      ],
      "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

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

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