Slop Eval vs Build

In-depth architectural comparison of the Slop Eval and Build 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 Slop Eval 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).
• You have access to required keys: ANTHROPIC_API_KEY.
• Primary tools included: LLM-based UI genericness scoring, Screenshot and URL input modes, Three-category versioned rubric.

Explore Slop Eval Details

Choose Build 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: Schema-validated structured JSON output, Human-readable MCP content output, TypeScript compiler support.

Feature & Specification Comparison

Specification	Slop Eval Developer Tools	Build Developer Tools
Summary	Wraps the slop-eval CLI as a single generic MCP tool for genericness scoring of AI UI output.	Structured build tool output (tsc, generic commands) as typed JSON diagnostics.
Category & Scope	Developer Tools	Developer Tools
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": {
    "slop-eval": {
      "command": "npx",
      "args": [
        "-y",
        "slop-eval-cli"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "build": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/init"
      ]
    }
  }
}

Related MCP Server Comparisons