What is the key difference between SandBase CLI and MCPDiscovery?

SandBase CLI belongs to the Aggregators category with cloud HTTP/SSE execution, while MCPDiscovery belongs to the Aggregators category with local stdio execution.

How do I install SandBase CLI or MCPDiscovery in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are SandBase CLI and MCPDiscovery free or paid?

SandBase CLI operates under a Free / Open Source model (other). MCPDiscovery operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

SandBase CLI lists 6 tools with 11 views and 188 GitHub stars. MCPDiscovery lists 6 tools with 2 views and 53 GitHub stars.

Can I use both SandBase CLI and MCPDiscovery together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

SandBase CLI vs MCPDiscovery

In-depth architectural comparison of the SandBase CLI and MCPDiscovery 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.

At a Glance & Executive Verdict

SandBase CLI

Aggregators · Remote HTTP/SSE

Quality: 65/100 (Great) | Auth: other

MCPDiscovery

Aggregators · Local stdio

Quality: 43/100 (Fair) | Auth: No auth required

Verdict Summary: Choose SandBase CLI if you need specialized Aggregators tools running via a hosted cloud SSE transport. Choose MCPDiscovery if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose SandBase CLI when:

You need dedicated capabilities in the Aggregators domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: sandbase_discover, sandbase_inspect, sandbase_run.

Explore SandBase CLI Details

Choose MCPDiscovery when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Quick search for explicit requirements, Deep search with planning, testing, and acting stages, Local and remote server discovery.

Explore MCPDiscovery Details

Feature & Specification Comparison

Specification	SandBase CLI Aggregators	MCPDiscovery particlefuture Aggregators
Summary	Open-source CLI and MCP server for discovering and calling 2,000+ AI models and APIs through one consistent developer interface.	MCP of MCPs. Automatic discovery and configure MCP servers on your local machine.
Category & Scope	Aggregators

Tools & Capabilities Breakdown

SandBase CLI Tools (6)

sandbase_discover

Search all 2,000+ available AI models and APIs

sandbase_inspect

Get input schema, pricing, and ready-to-use template

sandbase_run

Execute a model or API endpoint

sandbase_run_get

Poll status/result of an async run (video gen, etc.)

sandbase_runs

List your recent API calls with cost breakdown

sandbase_account

Check account balance (free, no cost)

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).

SandBase CLI Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sandbase-cli": {
      "url": "https://tensorblock.co/mcp/servers/github-sandbaseai-cli-c4e113db"
    }
  }
}

MCPDiscovery Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "particlefuture-mcpdiscovery": {
      "command": "npx",
      "args": [
        "-y",
        "@1mcpserver/1mcpserver"
      ]
    }
  }
}

Frequently Asked Questions

SandBase CLI is categorized under Aggregators and uses a remote streaming HTTP/SSE transport. In contrast, MCPDiscovery belongs to Aggregators using local stdio subprocess. Select SandBase CLI when you need capabilities focused on aggregators and MCPDiscovery when you require tools for aggregators.

More alternatives to SandBase CLI More alternatives to MCPDiscovery Aggregators category hub Canonical compare URL