Git vs SandBase CLI
A side-by-side look at the Git and SandBase CLI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for other tools and integrations work as a local process; choose SandBase CLI for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Aggregators |
| Quality signal | 89/100 · Excellent | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | other |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,289 | 186 |
| Directory activity | 39 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | 9 | 7 |
| Full listing | View Git | View SandBase CLI |
Tools & capabilities
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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
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.
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
SandBase CLI
{
"mcpServers": {
"sandbase-cli": {
"url": "https://tensorblock.co/mcp/servers/github-sandbaseai-cli-c4e113db"
}
}
}
Frequently asked questions
Git is categorized under Other Tools and Integrations and uses a local stdio subprocess. SandBase CLI belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Git for other tools and integrations work and SandBase CLI 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.
Git is listed as free. Auth: no auth required. SandBase CLI is listed as free. Auth: other. 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 git and sandbase-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars. SandBase CLI has 61/100 (Good) with 11 views, 0 installs and 186 GitHub stars.