mcpField
S
SandBase

SandBase

Remote
github.com/sandbaseaiAI & Agents185Updated 4d ago
Repository

About SandBase

SandBase lets AI agents access a catalog of models and data APIs through an MCP server, without managing provider keys individually. Its CLI authorizes and configures supported clients, and includes commands for catalog inspection and run status.

Key features

  1. 01Access a catalog of models and data APIs
  2. 02Configure supported clients with the CLI
  3. 03Discover endpoints and inspect schemas and prices
  4. 04Run synchronous or asynchronous jobs
  5. 05Check run status and account balance
  6. 06Upload local files for tool use

Use cases

  1. 01Search web or social media from an agent
  2. 02Generate images, video, or audio with models
  3. 03Review endpoint pricing and inputs before execution
  4. 04Check asynchronous results and recent run costs

MCP support

A local MCP bridge connects clients to the SandBase API and exposes tools for discovery, inspection, execution, run status, and account information. The CLI handles authorization and client setup; API calls use a SandBase account rather than individual provider keys.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://sandbase.ai/v1/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://sandbase.ai/v1/mcpAuth required

Tools

Details

From the project 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.

English | 中文 | 日本語 | 한국어 | Español | Français | Deutsch | Português

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:

set up https://www.sandbase.ai/SKILL.md

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

npx -y @sandbaseai/cli@latest connect

Or install the official Homebrew formula on macOS or Linux:

brew install sandbaseai/tap/sandbaseai-cli
sandbase connect

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 page
npx -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:

npx -y @sandbaseai/cli@latest catalog --json

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, finance100 free calls/day per organization, then paid per call (price shown by sandbase inspect)
Discovery, inspection, run status, balance, file uploadFree
Models — LLM, image, video, audioPaid 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:

  1. Use sandbase_discover to find candidates by task or capability.
  2. Use sandbase_inspect to read the current input schema, pricing, and execution requirements.
  3. 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.
  4. For asynchronous work, use sandbase_run_get with the returned run_id instead of creating a duplicate run.
  5. Use sandbase_runs to review recent run status and recorded cost.
  6. 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

CategoryToolsWhat You Can Do
Web SearchGoogle, Exa, Tavily, ScholarResearch anything in real-time
Social MediaTwitter/X, YouTube, Reddit, Instagram, TikTok, Xiaohongshu, Weibo, BilibiliMonitor trends, pull posts, analyze content
ScrapingFirecrawl, Exa ContentExtract data from any public webpage
AI ModelsGPT-4o, Claude, Gemini, DeepSeek, Qwen, LlamaRun any model without managing keys
Image GenFlux, DALL-E, Ideogram, RecraftCreate logos, illustrations, mockups
Video GenKling, MiniMax, Runway, LumaGenerate short clips and animations
AudioElevenLabs, WhisperText-to-speech, transcription
E-commerceTaobao, AmazonProduct research, price comparison
FinanceStock data, company infoMarket research and analysis

Supported Clients (25 Targets)

Works with every major AI coding tool:

Auto-configuredManual setup
Cursor, Cursor CLIChatGPT
Claude CodeClaude Desktop
Codex
Kiro IDE, Kiro CLI
Windsurf
Gemini CLI
Amp
Warp
OpenCode, Qwen Code, Kimi CLI
Hermes, OpenClaw

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

npx -y @sandbaseai/cli@latest catalog --json
# Connect all detected clients at once
npx -y @sandbaseai/cli@latest connect

# Or target one specific client
npx -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 openclaw
npx -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:

npx -y @sandbaseai/cli@latest unregister --client openclaw

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 hermes
npx -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:

npx -y @sandbaseai/cli@latest unregister --client hermes

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 │
│                 │◀────────│               │◀────────│                    │
└─────────────────┘         └───────────────┘         └────────────────────┘
  1. Run connect → CLI opens browser auth → you approve
  2. API key saved locally (file permissions 0600)
  3. MCP bridge configured for your client
  4. Agent calls tools on-demand. No daemon. No background process.

Commands

CLI Commands
sandbase connect [--client <name>]    # Authorize + configure
sandbase setup                        # After upgrading: refresh the local bridge + Skill, test connectivity
sandbase doctor [--client <name>]     # Local checks plus one real round trip to SandBase
sandbase unregister [--client <name>] # Remove configuration
sandbase 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|service
sandbase inspect sandbase_twitter_web_search_timeline       # fields, price, ready-to-run command
sandbase 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 disk
sandbase runs get -r <run_id> -w -o result.json            # resume a long run instead of re-running it
sandbase upload ./photo.png                                # local image/audio/video -> public URL for tools that take a URL
sandbase 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)
ToolPurpose
sandbase_discoverSearch all 2,000+ available AI models and APIs — free
sandbase_inspectGet input schema, current price, and a ready-to-run template — free
sandbase_runExecute a model or API endpoint — eligible data APIs: 100 free calls/day per organization, then paid per call; models: paid per call
sandbase_run_getPoll status/result of an async run (video gen, etc.) — free
sandbase_runsList your recent runs with their cost — free
sandbase_accountCheck account balance and today's free data API calls (free_api_quota) — free
sandbase_run_cancelCancel an Agent Service run — free

Recommended workflow:

discover → inspect → run
1. sandbase_discover(q: "twitter search")          → find current candidates
2. sandbase_inspect(name: discovered_name)          → get schema and pricing
3. 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

npx -y @sandbaseai/cli@latest connect

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.


Links

Community

Community-curated listings:

License

Apache-2.0

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.