MCP Memory Graph vs Statelessagent

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

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Freemium).
• Primary tools included: SQLite-based persistent local memory, Hybrid semantic and keyword search, Knowledge graph for linked entities and memories.

Explore MCP Memory Graph 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: 19 MCP tools for search, notes, decisions, and handoffs, SQLite FTS5 keyword search with optional Ollama semantic search, Provenance tracking and stale-note detection.

Feature & Specification Comparison

Specification	MCP Memory Graph Knowledge & Memory	Statelessagent sgx-labs Knowledge & Memory
Summary
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-memory-graph-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-memory-graph"
      ]
    }
  }
}

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

Related MCP Server Comparisons