Memory Kernel vs Memtether

In-depth architectural comparison of the Memory Kernel and Memtether 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 Kernel 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: SQLite FTS5 local retrieval, Structured memory records, Deterministic search and context packing.

Explore Memory Kernel Details

Choose Memtether 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: Shared SQLite memory database, Source attribution and provenance, Bi-temporal fact records.

Explore Memtether Details

Feature & Specification Comparison

Specification	Memory Kernel Databases	Memtether Databases
Summary	Local-first memory for AI agents: SQLite FTS5, deterministic recall, no vector DB, no cloud.	Cross-client AI memory hub: agents share one SQLite memory.db via file-level pointers.
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-kernel": {
      "command": "uvx",
      "args": [
        "amormorri-memory-kernel"
      ]
    }
  }
}

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

Related MCP Server Comparisons