Fidelis Memory vs Heartwood Memory

In-depth architectural comparison of the Fidelis Memory and Heartwood Memory 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 Fidelis Memory 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).

Explore Fidelis Memory Details

Choose Heartwood Memory 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).

Explore Heartwood Memory Details

Feature & Specification Comparison

Specification	Fidelis Memory Knowledge & Memory	Heartwood Memory Knowledge & Memory
Summary	Recall locally stored agent memories through an MCP-compatible host.	Governed agent recall with signed provenance and policy gates. BUSL-1.1; not OSI open source.
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "fidelis-memory": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

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

Related MCP Server Comparisons