A side-by-side look at the SandBase Harness and Sub Agents 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 Harness for coding agents work as a local process; choose Sub Agents MCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SandBase Harness when
You need dedicated capabilities in the Coding Agents domain.
No tool names declared yet. Check the project README from the listing page.
Sub Agents 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 Harness is categorized under Coding Agents and uses a local stdio subprocess. Sub Agents MCP belongs to Coding Agents and uses a local stdio subprocess. Pick SandBase Harness for coding agents work and Sub Agents MCP for coding agents.
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 Harness has no declared pricing — check the project's own site. Sub Agents MCP 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-harness and sub-agents-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SandBase Harness has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 640 GitHub stars. Sub Agents MCP has 49/100 (Fair) with 1 views, 0 installs and 99 GitHub stars.