SandBase CLI vs ToolRouter
A side-by-side look at the SandBase CLI and ToolRouter MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SandBase CLI for aggregators work over a hosted endpoint; choose ToolRouter for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SandBase CLI when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You want tools like
sandbase_discover, sandbase_inspect, sandbase_run.
Choose ToolRouter when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TOOLROUTER_API_KEY, TOOLROUTER_API_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 61/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | TOOLROUTER_API_KEYTOOLROUTER_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 186 | 0 |
| Directory activity | 11 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View SandBase CLI | View ToolRouter |
Tools & capabilities
SandBase CLI tools 7
sandbase_discoverSearch all 2,000+ available AI models and APIs — freesandbase_inspectGet input schema, current price, and a ready-to-run template — freesandbase_runExecute a model or API endpoint — free for data APIs, paid for modelssandbase_run_getPoll status/result of an async run (video gen, etc.) — freesandbase_runsList your recent runs with their cost — freesandbase_accountCheck account balance — freesandbase_run_cancelCancel an Agent Service run — free
ToolRouter tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SandBase CLI
{
"mcpServers": {
"sandbase-cli": {
"url": "https://tensorblock.co/mcp/servers/github-sandbaseai-cli-c4e113db"
}
}
}
ToolRouter
{
"mcpServers": {
"toolrouter": {
"command": "npx",
"args": [
"-y",
"toolrouter-mcp"
],
"env": {
"TOOLROUTER_API_KEY": "YOUR_TOOLROUTER_API_KEY_HERE",
"TOOLROUTER_API_URL": "YOUR_TOOLROUTER_API_URL_HERE"
}
}
}
}
Frequently asked questions
SandBase CLI is categorized under Aggregators and uses a remote HTTP/SSE transport. ToolRouter belongs to Aggregators and uses a local stdio subprocess. Pick SandBase CLI for aggregators work and ToolRouter for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SandBase CLI is listed as free. Auth: other. ToolRouter has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sandbase-cli and toolrouter as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SandBase CLI has a quality signal of 61/100 (Good) with 11 views, 0 installs and 186 GitHub stars. ToolRouter has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.