Fetchsandbox MCP vs Repomix
A side-by-side look at the Fetchsandbox MCP and Repomix MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fetchsandbox MCP for developer tools work as a local process; choose Repomix for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fetchsandbox MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
guide, find_bugs, fix_bug.
Choose Repomix when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pack_codebase, directory, compress.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 56/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 28,991 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | 23 |
| Full listing | View Fetchsandbox MCP | View Repomix |
Tools & capabilities
Fetchsandbox MCP tools 17
guideRoutes a symptom to a spec, workflow and known failure classfind_bugsAudits your project against known integration failure classes. No git remote needed — it reads the directory you point it atfix_bugReturns a `git diff` for one finding. Doesn't touch your filesget_jobRetrieve the same running job without starting another analysis or proofprove_fixRuns the failure against your code before and after the diff. Green only on a measured flipvalidate_integrationProves **your own code** against a provider, not that our twin works. Hands back a fresh twin per provider, then reads our request log to report what your app actually calledquickrunRuns one of OUR curated workflows against a bundled spec. Green here says the provider behaves as documented — it says nothing about your integrationrun_workflowThe same, on a sandbox you already have — this is where you re-run with a `scenario` armedverify_behaviorShows a failure class on **reference** handlers — buggy vs fixed. Not your codelist_workflowsWorkflows AND the failure scenarios a spec can inject, in one answercoachMulti-turn help building an integrationrun_all_workflowsRuns several workflows in one call- +5 more on the listing page
Repomix tools 23
pack_codebasePackage a local code directory into a consolidated XML file for AI analysisdirectoryAbsolute path to the directory to packcompress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.attach_packed_outputAttach an existing Repomix packed output file for AI analysispathPath to a directory containing repomix-output.xml or direct path to a packed repository XML filepack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysisremoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.- +11 more on 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.
Fetchsandbox MCP
{
"mcpServers": {
"mcp-292": {
"command": "npx",
"args": [
"-y",
"fetchsandbox-mcp"
]
}
}
}
Repomix
{
"mcpServers": {
"repomix": {
"command": "npx",
"args": [
"-y",
"repomix@latest"
]
}
}
}
Frequently asked questions
Fetchsandbox MCP is categorized under Developer Tools and uses a local stdio subprocess. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick Fetchsandbox MCP for developer tools work and Repomix for developer tools.
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.
Fetchsandbox MCP has no declared pricing — check the project's own site. Repomix 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 mcp-292 and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fetchsandbox MCP has a quality signal of 56/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 28,991 GitHub stars.