State Memory MCP vs Neural Memory

In-depth architectural comparison of the State Memory MCP and Neural Memory 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?

S

Choose State Memory 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).

Explore State Memory MCP Details

Choose Neural 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).

Explore Neural Memory Details

Feature & Specification Comparison

Specification	S State Memory MCP Knowledge & Memory	Neural Memory Knowledge & Memory
Summary	Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.	Persistent memory for AI agents — 55 MCP tools, spreading activation recall.
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": {
    "state-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "state-memory-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "neural-memory": {
      "command": "uvx",
      "args": [
        "neural-memory"
      ]
    }
  }
}

Related MCP Server Comparisons