MCP Js vs Next Devtools MCP
A side-by-side look at the MCP Js 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 MCP Js for code execution work over a hosted endpoint; 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 MCP Js when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
run_js, get_execution, get_execution_output.
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 | Code Execution | Developer Tools |
| Quality signal | 59/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 62 | 832 |
| Directory activity | 3 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 5 | 4 |
| Full listing | View MCP Js | View Next Devtools MCP |
Tools & capabilities
MCP Js tools 5
run_jsStateful: queue execution → `{execution_id}`. Stateless: run and return `{output, error?}`.get_executionPoll status/result of an execution.get_execution_outputRead paginated console output (line or byte).cancel_executionTerminate a running execution.list_executionsList executions and their status.
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.
MCP Js
{
"mcpServers": {
"r33drichards-mcp-js": {
"url": "http://localhost:8080/mcp"
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
MCP Js is categorized under Code Execution and uses a remote HTTP/SSE transport. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Js for code execution 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.
MCP Js is listed as free. Auth: api key required. 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 r33drichards-mcp-js and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Js has a quality signal of 59/100 (Good) with 3 views, 0 installs and 62 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.