SandBase

io.github.sandbaseaiPublished by GitHub account sandbaseaiv0.1.17Updated Oct 24, 2026

Connect MCP clients to 2,000+ AI models without managing provider API keys.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Media & Design AI & ML

Server details

Identifier: io.github.sandbaseai/cli
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account sandbaseai for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.sandbaseai%2Fcli.svg)](https://sourceweft.com/mcp/io.github.sandbaseai%2Fcli?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

SandBase connects an assistant to a catalog of 2,000+ AI models and data APIs, so it can search, scrape, generate media and run LLMs without managing provider…

What you can do: Discover and inspect catalog entries: search models and APIs by task, read input schemas, current pricing and ready-to-run templates
Run endpoints: execute LLM, image, video, audio and data API calls, with async runs polled by run id
Manage runs: list recent runs with recorded cost, cancel an Agent Service run
Account: check balance and today's remaining free data API calls
Coverage includes web search, social media, scraping, e-commerce and finance data sources
When to use it: Useful when an assistant needs live web, social or market data, or access to many LLM, image, video and audio models, without wiring up each provider's API key separately. Discovery and inspection are free, so it suits agents that survey options before spending.
Requirements: A remote endpoint at sandbase.ai plus a bearer credential in the Authorization header, obtained through a browser sign-in flow (the CLI's connect command). The README also documents an npm CLI and a Homebrew formula for local setup. A SandBase account is needed; paid usage draws on an account balance.

Before you install

Runs are billed: data APIs give 100 free calls per organization per UTC day, then cost per call, and models are paid per call or per token, so confirm the price with inspect before running. The bearer credential is a secret stored locally with restricted permissions and should be revoked if exposed. Runs send prompts and inputs to SandBase and its upstream providers, and uploads make local files publicly reachable by URL.

Installation

In SourceWeft

Open SandBase in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sandbaseai%2Fcli/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sandbase": {
      "type": "http",
      "url": "https://sandbase.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

@sandbaseai/cli

Give your AI agent superpowers. One line. 2,000+ AI models and APIs. 100 free data API calls a day, then pay per call from one balance.

[GitHub release] [CI] [Official MCP Registry] [Indexed on TensorBlock MCP Index] [License] [GitHub stars]

[SandBase CLI connects AI clients to 2,000+ AI models and APIs]

Your AI coding assistant is smart, but it's trapped in a box. It can't search the web, check social media, generate images, or access real-time data — unless you wire up each API yourself.

SandBase changes that. One command connects your agent to 2,000+ AI models and APIs through the Model Context Protocol. No API keys to manage. No configuration headaches.

Building directly over HTTP instead of MCP? Start with the SandBase API quickstart or compare the unified LLM, image, and video API with specialized model gateways.

Setup

Paste this into your agent and let it do the rest:

It reads the SandBase Skill, runs connect itself, and asks you to approve one browser sign-in. Prefer to drive it yourself:

Or install the official Homebrew formula on macOS or Linux:

See the Homebrew launch announcement and macOS/Linux CI evidence.

Approve the browser authorization once; each supported client can then discover, inspect, and run available SandBase models and APIs through the local MCP bridge. Start a new session afterwards so the sandbase_* tools load.

Every GitHub release publishes its own SHA-256 next to the tarball, so you can pin and verify an exact build instead of tracking latest:

V=$(npm view @sandbaseai/cli version)curl -fL -O "https://github.com/sandbaseai/cli/releases/download/v$V/sandbaseai-cli-$V.tgz"shasum -a 256 "sandbaseai-cli-$V.tgz"   # compare against the checksum on the release pagenpx -y "./sandbaseai-cli-$V.tgz" connect

V=$(npm view @sandbaseai/cli version)curl -fL -O "https://github.com/sandbaseai/cli/releases/download/v$V/sandbaseai-cli-$V.tgz"shasum -a 256 "sandbaseai-cli-$V.tgz"   # compare against the checksum on the release pagenpx -y "./sandbaseai-cli-$V.tgz" connect

Want to inspect compatibility before signing in or changing configuration? The client catalog is a read-only command — it writes nothing and needs no account:

[Read-only SandBase CLI catalog audit showing 25 client targets] [SandBase CLI doctor failing closed for an empty isolated profile]

_{A no-write catalog audit and a bounded doctor check against an empty isolated profile.}

Homebrew users can run the same read-only check with sandbase catalog --json.

What It Costs

	Price
Data APIs — search, social, scraping, e-commerce, finance	100 free calls/day per organization, then paid per call (price shown by `sandbase inspect`)
Discovery, inspection, run status, balance, file upload	Free
Models — LLM, image, video, audio	Paid per call or per million tokens

sandbase inspect <tool> always shows the current price before you run anything; data APIs covered by the daily allowance also show pricing.free_quota. The 100 free calls are shared across eligible data APIs and reset at 00:00 UTC; after that, calls are billed per call. sandbase balance --json shows today's remaining free calls as free_api_quota. Prices can change, so trust the live response over any example in this file.

Visit the official SandBase CLI project page for a compact overview. For a security-focused walkthrough of client detection, MCP tools, and rollback, read the 25-client SandBase CLI setup guide. AI agents and automated installers can use the concise llms-install.md instructions.

SandBase Open-Source Stack

SandBase Harness — self-hosted agent runtime with persistent sessions, sandbox isolation, approvals, audit, and replay.
SandBase Agent Skills — 88 installable Skills for research, social intelligence, marketing, and business workflows.
SandBase for Codex — official Codex plugin packaging the SandBase MCP bridge and guided Agent Skill; its required HOL security scan passes on main.

Discover the authenticated remote bridge in the official MCP Registry, read its Registry community showcase, or find it through Chinese Independent Developer, Awesome MCP, Glama, TensorBlock MCP Index, MCPRepository, VaultPlane, AIMCP, MCP Server Hub, MCP Server Spot, or the Awesome AI API Proxy. External maintainers have merged SandBase into Awesome Codex CLI, Awesome Agent Skills, and Awesome MCP Server. The Hermes integration is independently listed in the Hermes Atlas ecosystem catalog and as beta in Awesome Hermes Agent. Install its verified sandbase Agent Skill from skills.sh, the sandbaseai/cli/sandbase listing on SkillsCat, the sandbaseai/cli/sandbase listing on skills.re, the 93/100 verified SandBase listing on vSkill, the security-audited SandBase listing on Skillstore, or the versioned sandbaseai/sandbase snapshot on Agent Skill Hub.

A Verifiable Agent Workflow

After connecting, ask your agent to follow the same inspectable sequence for search, data APIs, language models, image generation, video generation, and other catalog capabilities:

Use sandbase_discover to find candidates by task or capability.
Use sandbase_inspect to read the current input schema, pricing, and execution requirements.
Confirm the selected endpoint and parameters before calling sandbase_run. Data APIs include 100 free calls per organization per UTC day, then are billed per call like models; confirm the cost shown by sandbase_inspect before paid runs.
For asynchronous work, use sandbase_run_get with the returned run_id instead of creating a duplicate run.
Use sandbase_runs to review recent run status and recorded cost.
Use sandbase_account to check the current account balance.

For example, start with a non-billable discovery request:

Find image models suitable for a square product illustration. Compare the required inputs and current pricing for the best two candidates. Do not run either model yet.

Discovery and inspection never cost anything, so an agent can always survey the catalog before it spends.

After reviewing the live response, explicitly approve the endpoint and inputs you want to run. Catalog entries, schemas, pricing, latency, and availability can change, so use the tool response from the current session rather than a static example.

See the complete Claude Code and Codex walkthrough or the Chinese workflow guide. For a live catalog example, read the GitHub connector discover-and-inspect dogfooding note.

What's Inside

Category	Tools	What You Can Do
Web Search	Google, Exa, Tavily, Scholar	Research anything in real-time
Social Media	Twitter/X, YouTube, Reddit, Instagram, TikTok, Xiaohongshu, Weibo, Bilibili	Monitor trends, pull posts, analyze content
Scraping	Firecrawl, Exa Content	Extract data from any public webpage
AI Models	GPT-4o, Claude, Gemini, DeepSeek, Qwen, Llama	Run any model without managing keys
Image Gen	Flux, DALL-E, Ideogram, Recraft	Create logos, illustrations, mockups
Video Gen	Kling, MiniMax, Runway, Luma	Generate short clips and animations
Audio	ElevenLabs, Whisper	Text-to-speech, transcription
E-commerce	Taobao, Amazon	Product research, price comparison
Finance	Stock data, company info	Market research and analysis

Supported Clients (25 Targets)

Works with every major AI coding tool:

Preview the complete compatibility catalog without signing in or changing any files:

# Connect all detected clients at oncenpx -y @sandbaseai/cli@latest connect
# Or target one specific clientnpx -y @sandbaseai/cli@latest connect --client cursor

# Connect all detected clients at oncenpx -y @sandbaseai/cli@latest connect
# Or target one specific clientnpx -y @sandbaseai/cli@latest connect --client cursor

OpenClaw quickstart

Target OpenClaw directly, then ask the CLI to read back the managed MCP server and SandBase Skill before you rely on them:

npx -y @sandbaseai/cli@latest connect --client openclawnpx -y @sandbaseai/cli@latest doctor --client openclaw

npx -y @sandbaseai/cli@latest connect --client openclawnpx -y @sandbaseai/cli@latest doctor --client openclaw

After doctor reports the credential, MCP bridge, and Skill as configured, restart OpenClaw and make a natural-language request that needs SandBase. If OpenClaw already has a non-SandBase MCP server named sandbase, the installer leaves it untouched instead of overwriting it. To remove the managed MCP entry and local credential later:

OpenClaw currently exposes no supported Skill removal command, so unregister reports that limitation and leaves the verified SandBase Skill installed.

Hermes quickstart

SandBase can install both its managed Hermes Skill and local MCP entry in one authorization transaction:

npx -y @sandbaseai/cli@latest connect --client hermesnpx -y @sandbaseai/cli@latest doctor --client hermes

npx -y @sandbaseai/cli@latest connect --client hermesnpx -y @sandbaseai/cli@latest doctor --client hermes

doctor verifies the owned local credential, MCP entry, and Skill. Restart Hermes to confirm native discovery in a fresh client session, then use the SandBase Skill or MCP tools. A pre-existing, non-SandBase MCP entry named sandbase is left untouched. To remove only the managed Hermes configuration, Skill, and local credential while retaining the shared bridge for other clients:

The integration is independently listed by Hermes Atlas and Awesome Hermes Agent.

How It Works

┌─────────────────┐         ┌───────────────┐         ┌────────────────────┐│   Your Agent    │  MCP    │  Local Bridge │  HTTPS  │    SandBase API     ││  (Cursor, etc.) │────────▶│  (on-demand)  │────────▶│ 2,000+ models/APIs ││                 │◀────────│               │◀────────│                    │└─────────────────┘         └───────────────┘         └────────────────────┘

┌─────────────────┐         ┌───────────────┐         ┌────────────────────┐│   Your Agent    │  MCP    │  Local Bridge │  HTTPS  │    SandBase API     ││  (Cursor, etc.) │────────▶│  (on-demand)  │────────▶│ 2,000+ models/APIs ││                 │◀────────│               │◀────────│                    │└─────────────────┘         └───────────────┘         └────────────────────┘

Run connect → CLI opens browser auth → you approve
API key saved locally (file permissions 0600)
MCP bridge configured for your client
Agent calls tools on-demand. No daemon. No background process.

Commands

CLI Commands

sandbase connect [--client <name>]    # Authorize + configuresandbase setup                        # After upgrading: refresh the local bridge + Skill, test connectivitysandbase doctor [--client <name>]     # Local checks plus one real round trip to SandBasesandbase unregister [--client <name>] # Remove configurationsandbase catalog --json               # List all supported clients

sandbase connect [--client <name>]    # Authorize + configuresandbase setup                        # After upgrading: refresh the local bridge + Skill, test connectivitysandbase doctor [--client <name>]     # Local checks plus one real round trip to SandBasesandbase unregister [--client <name>] # Remove configurationsandbase catalog --json               # List all supported clients

Agent Commands (shell transport, same capabilities as the MCP tools)

Agents without MCP, or with a broken MCP session, use the same catalog from a shell. Credentials come from connect automatically (or SANDBASE_API_KEY / sandbase keys add -k <key>).

sandbase discover -q "twitter posts"                       # search; -t api|llm|multimodal|embedding|servicesandbase inspect sandbase_twitter_web_search_timeline       # fields, price, ready-to-run commandsandbase run sandbase_twitter_web_search_timeline -i '{"keyword":"AI agents"}'sandbase run <video_tool> -i '{"prompt":"..."}' -w -o result.json   # wait with backoff, save output to disksandbase runs get -r <run_id> -w -o result.json            # resume a long run instead of re-running itsandbase upload ./photo.png                                # local image/audio/video -> public URL for tools that take a URLsandbase runs list | sandbase balance

sandbase discover -q "twitter posts"                       # search; -t api|llm|multimodal|embedding|servicesandbase inspect sandbase_twitter_web_search_timeline       # fields, price, ready-to-run commandsandbase run sandbase_twitter_web_search_timeline -i '{"keyword":"AI agents"}'sandbase run <video_tool> -i '{"prompt":"..."}' -w -o result.json   # wait with backoff, save output to disksandbase runs get -r <run_id> -w -o result.json            # resume a long run instead of re-running itsandbase upload ./photo.png                                # local image/audio/video -> public URL for tools that take a URLsandbase runs list | sandbase balance

-j prints JSON; errors are {"error":{"code","message","hint"}} with the next step in hint. Exit codes: 0 success or still running, 1 failure (including a failed run), 2 usage.

Sync tools (LLMs, most data APIs) return their result directly; async tools (image, video, audio jobs) return a run id — wait with -w, or fetch later with sandbase runs get -r <run_id>. If api.sandbase.ai is unreachable, the bridge keeps the SandBase tools visible with an actionable error instead of dropping the server.

MCP Tools (available to your agent after connecting)

Tool	Purpose
`sandbase_discover`	Search all 2,000+ available AI models and APIs — free
`sandbase_inspect`	Get input schema, current price, and a ready-to-run template — free
`sandbase_run`	Execute a model or API endpoint — eligible data APIs: 100 free calls/day per organization, then paid per call; models: paid per call
`sandbase_run_get`	Poll status/result of an async run (video gen, etc.) — free
`sandbase_runs`	List your recent runs with their cost — free
`sandbase_account`	Check account balance and today's free data API calls (`free_api_quota`) — free
`sandbase_run_cancel`	Cancel an Agent Service run — free

Recommended workflow:

1. sandbase_discover(q: "twitter search")          → find current candidates2. sandbase_inspect(name: discovered_name)          → get schema and pricing3. sandbase_run(name: discovered_name, input: {...}) → run after confirmation

1. sandbase_discover(q: "twitter search")          → find current candidates2. sandbase_inspect(name: discovered_name)          → get schema and pricing3. sandbase_run(name: discovered_name, input: {...}) → run after confirmation

Security

Zero secrets in URLs or CLI args — OAuth device flow with PKCE
Restricted file permissions — Credentials stored with 0600
Ownership-aware updates — Existing JSONC comments and user-managed MCP entries are preserved
Exact rollback — On failure or unregister, only configuration owned by SandBase is removed
Revoke anytime — One click in the SandBase Dashboard

Get Started

Then ask your agent to do something it couldn't before.

Create an account → — every organization gets 100 free data API calls a day.

If SandBase saves you setup time, star the repository — it helps more agent users discover the project.

Community

Community-curated listings:

License

Apache-2.0

Source: README.md at commit 844c8b0

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v0.1.17LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Auto-configured	Manual setup
Cursor, Cursor CLI	ChatGPT
Claude Code	Claude Desktop
Codex
Kiro IDE, Kiro CLI
Windsurf
Gemini CLI
Amp
Warp
OpenCode, Qwen Code, Kimi CLI
Hermes, OpenClaw