Next Devtools MCP vs Xplainable MCP Server
A side-by-side look at the Next Devtools MCP and Xplainable MCP Server 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 Xplainable MCP Server for data science tools as a local process. 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 Xplainable MCP Server when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Data Science Tools |
| Quality signal | 86/100 · Excellent | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 832 | 1 |
| Directory activity | 9 views 0 installs 1 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Next Devtools MCP | View Xplainable MCP Server |
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.
Xplainable MCP Server 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"
]
}
}
}
Xplainable MCP Server
{
"mcpServers": {
"xplainable-mcp-server": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/xplainable/xplainable-mcp-server.git",
"xplainable-mcp"
]
}
}
}
Frequently asked questions
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Xplainable MCP Server belongs to Data Science Tools and uses a local stdio subprocess. Pick Next Devtools MCP for developer tools work and Xplainable MCP Server for data science 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.
Next Devtools MCP is listed as free. Auth: no auth required. Xplainable MCP Server 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 vercel-next-devtools-mcp and xplainable-mcp-server 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. Xplainable MCP Server has 39/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.