Claude Code Explorer MCP vs Next Devtools MCP

A side-by-side look at the Claude Code Explorer 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.

Claude Code Explorer MCP logoClaude Code Explorer MCPDeveloper Tools · Local subprocess (stdio)Explore the Claude Code CLI source — browse tools, commands, search code, and more.61GoodAuth: not declaredNext Devtools MCP logoNext Devtools MCPDeveloper Tools · Local subprocess (stdio)Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.86ExcellentAuth: no auth required

Verdict: choose Claude Code Explorer 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?

Claude Code Explorer MCP logoChoose Claude Code Explorer MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: CLAUDE_CODE_SRC_ROOT.
  • You want tools like list_tools, list_commands, get_tool_source.
Explore Claude Code Explorer MCP

Next Devtools MCP logoChoose 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.
Explore Next Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClaude Code Explorer MCP logoClaude Code Explorer MCPNext Devtools MCP logoNext Devtools MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal61/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsCLAUDE_CODE_SRC_ROOTNone listed
Verified ownerCommunity listing Verified
GitHub stars3,406832
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 1 upvotes
Tools84

Tools & capabilities

Claude Code Explorer MCP tools 8

  • list_toolsList all ~40 agent tools with source files
  • list_commandsList all ~50 slash commands with source files
  • get_tool_sourceRead full source of any tool (e.g. BashTool, FileEditTool)
  • get_command_sourceRead source of any slash command (e.g. review, mcp)
  • read_source_fileRead any file from `src/` by path
  • search_sourceGrep across the entire source tree
  • list_directoryBrowse `src/` directories
  • get_architectureHigh-level architecture overview

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.

Claude Code Explorer MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "claude-code-explorer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "warrioraashuu-codemaster"
      ],
      "env": {
        "CLAUDE_CODE_SRC_ROOT": "YOUR_CLAUDE_CODE_SRC_ROOT_HERE"
      }
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Claude Code Explorer 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 Claude Code Explorer 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.

Claude Code Explorer 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 claude-code-explorer-mcp and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Claude Code Explorer MCP has a quality signal of 61/100 (Good) with 1 views, 0 installs and 3,406 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 832 GitHub stars.