Agentkits Memory vs Engram Mcp

In-depth architectural comparison of the Agentkits Memory and Engram 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 Agentkits 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: 100% local SQLite database storage with no cloud or API keys, Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity, Automatic session tracking and context injection via hooks.

Explore Agentkits Memory Details

Choose Engram 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).
• You have access to required keys: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
• Primary tools included: SQLite-backed local memory storage, Semantic search using Ollama nomic-embed-text embeddings, Keyword search fallback if embeddings are unavailable.

Feature & Specification Comparison

Specification	Agentkits Memory aitytech Knowledge & Memory	Engram Mcp Cartisien Knowledge & Memory
Summary	Persistent memory for AI coding assistants with hybrid search (FTS5 + vector embeddings), session tracking, automatic context hooks, and web viewer. SQLite-based with no daemon process — works with Claude Code, Cursor, Windsurf, and any MCP client.	Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
Category & Scope

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": {
    "aitytech-agentkits-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@aitytech/agentkits-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "cartisien-engram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cartisien/engram-mcp"
      ],
      "env": {
        "ENGRAM_DB": "YOUR_ENGRAM_DB_HERE",
        "ENGRAM_EMBEDDING_URL": "YOUR_ENGRAM_EMBEDDING_URL_HERE"
      }
    }
  }
}

Related MCP Server Comparisons