What is the key difference between Engram MCP and Memento?

Engram MCP belongs to the Knowledge & Memory category with local stdio execution, while Memento belongs to the Knowledge & Memory category with local stdio execution.

How do I install Engram MCP or Memento 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 Memento free or paid?

Engram MCP operates under a Free / Open Source model (No auth required). Memento operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Engram MCP lists 11 tools with 2 views and 1 GitHub stars. Memento lists 22 tools with 0 views and 0 GitHub stars.

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

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

Memento

Knowledge & Memory · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Verdict Summary: Choose Engram MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Memento 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 Memento 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: remember, recall, feedback.

Explore Memento Details

Feature & Specification Comparison

Specification	Engram MCP Cartisien Knowledge & Memory	Memento 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.	Agent memory MCP server with 4-type cognitive memory, hybrid search, and TTL-based forgetting.
Category & Scope	Knowledge & Memory

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.

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"
      }
    }
  }
}

Memento Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memento-2": {
      "command": "npx",
      "args": [
        "-y",
        "memento-mcp-server@latest"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Engram MCP More alternatives to Memento Knowledge & Memory category hub