Engram MCP vs Statelessagent

In-depth architectural comparison of the Engram MCP and Statelessagent 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 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: remember, recall, search.

Explore Engram MCP Details

Choose Statelessagent when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• Primary tools included: Provenance tracking and stale knowledge detection, Dual-layer memory with atomic fact extraction, 19 MCP tools for session handoffs, decisions, and search.

Feature & Specification Comparison

Specification	Engram MCP Cartisien Knowledge & Memory	Statelessagent sgx-labs Knowledge & Memory
Summary	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.	Memory with provenance tracking — records where agent knowledge originated and detects when sources change. 17 MCP tools for session handoffs, decisions, semantic search, and knowledge graph. Works across Claude Code, Cursor, Windsurf, Codex CLI, and Gemini CLI. Single Go binary, SQLite + vector search, fully local.
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": {
    "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"
      }
    }
  }
}

{
  "mcpServers": {
    "sgx-labs-statelessagent": {
      "command": "npx",
      "args": [
        "-y",
        "same@latest"
      ]
    }
  }
}

Related MCP Server Comparisons