Heartwood Memory vs Dataecho MCP

In-depth architectural comparison of the Heartwood Memory and Dataecho MCP 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 Heartwood Memory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Heartwood Memory Details

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

Explore Dataecho MCP Details

Feature & Specification Comparison

Specification	Heartwood Memory Knowledge & Memory	Dataecho MCP Knowledge & Memory
Summary	Governed agent recall with signed provenance and policy gates. BUSL-1.1; not OSI open source.	Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.
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": {
    "heartwood-memory": {
      "url": "https://heartwoodmemory.com/"
    }
  }
}

{
  "mcpServers": {
    "mcp-9": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Related MCP Server Comparisons