Cogmemory MCP vs Selvedge

In-depth architectural comparison of the Cogmemory MCP and Selvedge 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?

C

Choose Cogmemory MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: start_session, end_session, get_session_summary.

Explore Cogmemory MCP Details

Choose Selvedge when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: log_change, diff, blame.

Explore Selvedge Details

Feature & Specification Comparison

Specification	C Cogmemory MCP Developer Tools	Selvedge masondelan Developer Tools
Summary	CogMemory MCP Server — Unified context subsystems for AI coding agents	Change tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.
Category & Scope	Developer Tools

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": {
    "cogmemory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "cogmemory-mcp@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "masondelan-selvedge": {
      "command": "uvx",
      "args": [
        "selvedge"
      ]
    }
  }
}

Related MCP Server Comparisons