What is the key difference between Liquid and SandBase CLI?

Liquid belongs to the Aggregators category with local stdio execution, while SandBase CLI belongs to the Aggregators category with local stdio execution.

How do I install Liquid or SandBase CLI 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 Liquid and SandBase CLI free or paid?

Liquid operates under a Free / Open Source model (API Key required). SandBase CLI operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

Liquid lists 6 tools with 4 views and 2 GitHub stars. SandBase CLI lists 6 tools with 9 views and 146 GitHub stars.

Can I use both Liquid and SandBase CLI 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

Liquid vs SandBase CLI

In-depth architectural comparison of the Liquid 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.

At a Glance & Executive Verdict

Liquid

Aggregators · Local stdio

Quality: 51/100 (Good) | Auth: API Key required

SandBase CLI

Aggregators · Local stdio

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

Verdict Summary: Choose Liquid if you need specialized Aggregators tools running via a local process. Choose SandBase CLI 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 Liquid when:

You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: Discovers APIs and database interfaces, Maps responses to typed records, Supports fetch, query, write, and sense operations.

Explore Liquid Details

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.

Explore SandBase CLI Details

Feature & Specification Comparison

Specification	Liquid ertad-family Aggregators	S SandBase CLI Aggregators
Summary	Connect your agent to any HTTP API on the fly — discovers + maps any REST API once, then fetches typed data deterministically (no per-call LLM). Self-hosted MCP server (uvx --from 'liquid-api[mcp]' liquid-mcp); works with OpenAI/Gemini/Anthropic/local or any provider via LiteLLM. Open source (AGPL).	Open-source CLI and MCP server for discovering and calling 2,000+ AI models and APIs through one consistent developer interface.
Category & Scope	Aggregators

Tools & Capabilities Breakdown

Liquid Tools (6)

Discovers APIs and database interfaces

Maps responses to typed records

Supports fetch, query, write, and sense operations

Handles pagination and output normalization

Provides server-side search and aggregation

Returns structured recovery information

SandBase CLI Tools (6)

sandbase_discover

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

Liquid Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ertad-family-liquid": {
      "command": "uvx",
      "args": [
        "liquid-mcp"
      ]
    }
  }
}

SandBase CLI Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Liquid is categorized under Aggregators and uses a local stdio subprocess. In contrast, SandBase CLI belongs to Aggregators using local stdio subprocess. Select Liquid when you need capabilities focused on aggregators and SandBase CLI when you require tools for aggregators.

More alternatives to Liquid More alternatives to SandBase CLI Aggregators category hub