Fetchsandbox MCP vs Next Devtools MCP
A side-by-side look at the Fetchsandbox MCP and Next Devtools MCP 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 Next Devtools MCP 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 Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 56/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 1 | 832 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 17 | 4 |
| Full listing | View Fetchsandbox MCP | View Next Devtools MCP |
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
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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"
]
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Fetchsandbox MCP is categorized under Developer Tools and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Fetchsandbox MCP for developer tools work and Next Devtools MCP 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. Next Devtools 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 mcp-292 and vercel-next-devtools-mcp 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. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.