Selvedge vs Codesurface

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

Choose Codesurface 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: search, get_signature, get_class.

Explore Codesurface Details

Feature & Specification Comparison

Specification	Selvedge masondelan Developer Tools	Codesurface Developer Tools
Summary	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.	Indexes your codebase's public API and serves it via compact MCP tool responses.
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": {
    "masondelan-selvedge": {
      "command": "uvx",
      "args": [
        "selvedge"
      ]
    }
  }
}

{
  "mcpServers": {
    "codesurface": {
      "command": "uvx",
      "args": [
        "codesurface",
        "--project",
        "/path/to/your/src"
      ]
    }
  }
}

Related MCP Server Comparisons