Cinderwright API vs SandBase CLI

In-depth architectural comparison of the Cinderwright API and SandBase CLI 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 Cinderwright API when:

• You need dedicated capabilities in the Aggregators domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• You have access to required keys: CW_KEY.
• Primary tools included: Unified API endpoint for multiple payment protocols, Automatic protocol detection and payment routing, Supports USDC on Base (x402) and Bitcoin Lightning (L402).

Explore Cinderwright API Details

S

Choose SandBase CLI when:

• You need dedicated capabilities in the Aggregators domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: other (Free / Open Source).
• Primary tools included: sandbase_discover, sandbase_inspect, sandbase_run.

Feature & Specification Comparison

Specification	Cinderwright API cinderwright-ai Aggregators	S SandBase CLI Aggregators
Summary
Category & Scope	Aggregators	Aggregators
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": {
    "cinderwright-ai-cinderwright-api": {
      "command": "npx",
      "args": [
        "-y",
        "cinderwright"
      ],
      "env": {
        "CW_KEY": "YOUR_CW_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "sandbase-cli": {
      "command": "npx",
      "args": [
        "-y",
        "https"
      ]
    }
  }
}

Related MCP Server Comparisons