Engram vs Memphora

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

Which MCP Server Should You Choose?

E

Choose Engram 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: create_conversation, append_messages, search.

Explore Engram Details

Choose Memphora 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: memphora_search, memphora_store, memphora_extract_conversation.

Explore Memphora Details

Feature & Specification Comparison

Specification	E Engram Knowledge & Memory	Memphora Knowledge & Memory
Summary	Persistent memory for AI agents — verbatim conversations, searchable by meaning.	Add persistent memory to AI assistants. Store and recall info across conversations.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "engram-2": {
      "command": "npx",
      "args": [
        "-y",
        "@getengram/cli"
      ]
    }
  }
}

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

Related MCP Server Comparisons