SparkleTree vs WORKS Public Verifier

In-depth architectural comparison of the SparkleTree and WORKS Public Verifier 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 SparkleTree when:

• You need dedicated capabilities in the Version Control domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore SparkleTree Details

Choose WORKS Public Verifier when:

• You need dedicated capabilities in the Version Control domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore WORKS Public Verifier Details

Feature & Specification Comparison

Specification	S SparkleTree Version Control	WORKS Public Verifier Version Control
Summary	Create, publish and measure SparkleTree marketing campaigns from an AI client. OAuth 2.1 with PKCE.	Independent static verification for exact immutable public GitHub commits.
Category & Scope	Version Control	Version Control

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": {
    "sparkletree-2": {
      "url": "https://gitlab.com/sparkletree/sparkletree-plugin"
    }
  }
}

{
  "mcpServers": {
    "works-public-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "github"
      ]
    }
  }
}

Related MCP Server Comparisons