Next Devtools MCP vs Zambo
A side-by-side look at the Next Devtools MCP and Zambo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Next Devtools MCP for developer tools work as a local process; choose Zambo for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Zambo when
- You need dedicated capabilities in the Version Control domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Version Control |
| Quality signal | 86/100 · Excellent | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 832 | — |
| Directory activity | 9 views 0 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Next Devtools MCP | View Zambo |
Tools & capabilities
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.
Zambo 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.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Zambo
No confirmed install command for Zambo yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Zambo belongs to Version Control and uses an install path we have not confirmed yet. Pick Next Devtools MCP for developer tools work and Zambo for version control.
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. Zambo has no confirmed install command yet — follow its own setup instructions.
Next Devtools MCP is listed as free. Auth: no auth required. Zambo 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 vercel-next-devtools-mcp and zambo-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Next Devtools MCP has a quality signal of 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars. Zambo has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.