@squadbase/mcp

MCP Toolbox Launcher - a lightweight CLI that spawns MCP server packages on demand without installing their dependencies directly.

Why Use the Launcher?

Instead of bundling all database/cloud SDKs into a single package, each MCP server is a separate npm package. The launcher dynamically spawns only the server you need via npx, keeping dependencies isolated and install times fast.

Installation

# No installation needed - use npx
npx -y @squadbase/mcp <server>

# Or install globally
npm install -g @squadbase/mcp
mcp <server>

Usage

# Show help
mcp --help

# Run Databricks server
mcp databricks

# Run Redshift server
mcp redshift

# Pass arguments to server
mcp databricks --help

Available Servers

| Server | Package | Description | |--------|---------|-------------| | databricks | @squadbase/mcp-databricks | Databricks SQL & Unity Catalog | | redshift | @squadbase/mcp-redshift | Amazon Redshift |

Environment Variables

| Variable | Description | Default | |----------|-------------|---------| | MCP_TOOLBOX_SCOPE | npm scope for server packages | @squadbase | | MCP_TOOLBOX_VERSION | Pin server package version | (latest) |

Examples

Custom npm scope:

MCP_TOOLBOX_SCOPE="@acme" mcp databricks
# Spawns: npx -y @acme/mcp-databricks

Pinned version:

MCP_TOOLBOX_VERSION="0.2.1" mcp databricks
# Spawns: npx -y @squadbase/[email protected]

MCP Client Configuration

Add to your mcp.json for stdio-based clients:

{
  "mcpServers": {
    "databricks": {
      "command": "npx",
      "args": ["-y", "@squadbase/mcp", "databricks"],
      "env": {
        "DATABRICKS_HOST": "your-workspace.cloud.databricks.com",
        "DATABRICKS_TOKEN": "your-token",
        "DATABRICKS_HTTP_PATH": "/sql/1.0/warehouses/abc123def456"
      }
    },
    "redshift": {
      "command": "npx",
      "args": ["-y", "@squadbase/mcp", "redshift"],
      "env": {
        "REDSHIFT_HOST": "your-cluster.region.redshift.amazonaws.com",
        "REDSHIFT_PORT": "5439",
        "REDSHIFT_DATABASE": "dev",
        "REDSHIFT_USERNAME": "admin",
        "REDSHIFT_PASSWORD": "your-password"
      }
    }
  }
}

How It Works

When you run mcp databricks, the launcher:

1. Validates that "databricks" is a known server
2. Builds the package name: @squadbase/mcp-databricks
3. Spawns: npx -y @squadbase/mcp-databricks
4. Inherits stdio and forwards the exit code

The launcher itself has no dependencies on MCP SDK or any database/cloud SDKs.

License

MIT