Next Devtools MCP vs Xmp4 — Semantic Code Intelligence
A side-by-side look at the Next Devtools MCP and Xmp4 — Semantic Code Intelligence 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 Xmp4 — Semantic Code Intelligence for developer tools over a hosted endpoint. 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 Xmp4 — Semantic Code Intelligence when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
xmp4_callees, xmp4_callers, xmp4_deps.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 1 views 0 installs 0 upvotes |
| Tools | 4 | 16 |
| Full listing | View Next Devtools MCP | View Xmp4 — Semantic Code Intelligence |
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.
Xmp4 — Semantic Code Intelligence tools 16
xmp4_calleesFind direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.xmp4_callersFind direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.xmp4_depsList external dependencies of a project.xmp4_grepServer-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).xmp4_guideUsage guide for xmp4 tools — read this first to learn the correct workflowxmp4_hierarchyGet type hierarchy (base, interfaces, derived) for a symbol in a project.xmp4_infoGet detailed information about a symbol in a project.xmp4_outlineGet outline (all symbols) for a file in a project.xmp4_projectsSearch and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.xmp4_searchSearch symbols in a project. Use xmp4_projects first to find the project identifier.xmp4_serverGet server information, version, and capabilitiesxmp4_sourceExtract source code for a symbol in a project.- +4 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.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Xmp4 — Semantic Code Intelligence
{
"mcpServers": {
"xmp4-semantic-code-intelligence": {
"url": "https://mcp.example4.ai/mcp"
}
}
}
Frequently asked questions
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Xmp4 — Semantic Code Intelligence belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Next Devtools MCP for developer tools work and Xmp4 — Semantic Code Intelligence 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.
Next Devtools MCP is listed as free. Auth: no auth required. Xmp4 — Semantic Code Intelligence 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 xmp4-semantic-code-intelligence 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. Xmp4 — Semantic Code Intelligence has 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars.