MCP External Memory vs Tillpad

In-depth architectural comparison of the MCP External Memory and Tillpad 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 MCP External 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).
• Primary tools included: memory_store, memory_search, memory_get.

Explore MCP External Memory Details

T

Choose Tillpad 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).
• Primary tools included: usage_get, usage_periods_list, budget_get.

Explore Tillpad Details

Feature & Specification Comparison

Specification	MCP External Memory Knowledge & Memory	T Tillpad Knowledge & Memory
Summary	An MCP server that gives LLMs persistent, searchable semantic memory	Bounded KVP, RAG search, and wipe receipts for agent jobs over remote MCP
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": {
    "mcp-external-memory": {
      "command": "uvx",
      "args": [
        "mcp-external-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "tillpad-2": {
      "url": "https://tillpad.cnrcode.com/mcp"
    }
  }
}

Related MCP Server Comparisons