Memory Engine MCP vs Memory Vault

In-depth architectural comparison of the Memory Engine MCP and Memory Vault 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?

Choose Memory Engine MCP when:

• You need dedicated capabilities in the Databases domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: remember, recall, working_set.

Explore Memory Engine MCP Details

Choose Memory Vault when:

• You need dedicated capabilities in the Databases domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: recall, remember, forget.

Explore Memory Vault Details

Feature & Specification Comparison

Specification	Memory Engine MCP Databases	Memory Vault Databases
Summary	Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.	Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
Category & Scope	Databases	Databases
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": {
    "memory-engine-mcp": {
      "url": "https://img.shields.io/badge/version-1.7.0-blue"
    }
  }
}

{
  "mcpServers": {
    "memory-vault": {
      "command": "npx",
      "args": [
        "-y",
        "memory-vault"
      ]
    }
  }
}

Related MCP Server Comparisons