Linksee Memory vs Statelessagent

In-depth architectural comparison of the Linksee Memory 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 Linksee 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: Local SQLite memory shared across coding agents, Session-start decision and context recall, Anchored pre-action warnings for edits, writes, and shell commands.

Explore Linksee Memory 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	Linksee Memory michielinksee Knowledge & Memory	Statelessagent sgx-labs Knowledge & Memory
Summary	Local-first cross-agent memory with a 6-layer structure, Ebbinghaus-style forgetting curve, and drift detection that catches when code diverges from past decisions. One SQLite file shared across Claude Code, Cursor, Codex, and Gemini — no account or API key. npx linksee-memory	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": {
    "michielinksee-linksee-memory": {
      "command": "npx",
      "args": [
        "-y",
        "linksee-memory"
      ]
    }
  }
}

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

Related MCP Server Comparisons