SandBase CLI vs Scrivener MCP
A side-by-side look at the SandBase CLI and Scrivener MCP 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 Scrivener MCP for knowledge & memory 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 Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Knowledge & Memory |
| Quality signal | 61/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 186 | 67 |
| Directory activity | 11 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 7 | Not listed |
| Full listing | View SandBase CLI | View Scrivener MCP |
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
Scrivener MCP 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"
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
SandBase CLI is categorized under Aggregators and uses a remote HTTP/SSE transport. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick SandBase CLI for aggregators work and Scrivener MCP for knowledge & memory.
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. Scrivener MCP is listed as free. Auth: no auth required. 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 writerslogic-scrivener-mcp 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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.