Screenpipe vs State Memory MCP

In-depth architectural comparison of the Screenpipe and State Memory 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 Screenpipe 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 Screenpipe Details

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

Feature & Specification Comparison

Specification	Screenpipe Knowledge & Memory	S State Memory MCP Knowledge & Memory
Summary	Local-first workflow memory for AI agents. screenpipe lets MCP clients search selected screen, audio, app, and meeting context and turn real work into cited notes, SOPs, workflow reports, and automation candidates.	Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe"
      ]
    }
  }
}

{
  "mcpServers": {
    "state-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "state-memory-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons