How do I connect Next Devtools MCP Server to Claude?

Run `claude mcp add next-devtools-mcp -- npx -y add-mcp next-devtools-mcp@latest` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Next Devtools MCP Server free?

MCPVault has not verified a licence for this server. Check the upstream terms and pricing before use; connected APIs may require a paid account.

What can Next Devtools MCP Server do?

Next Devtools MCP Server documents 11 tools to the agent, including browser_eval, get_errors, get_logs. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Next Devtools MCP

Unclaimed

by vercel

Next.js Development for Coding Agent

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'next-devtools-mcp' -- 'npx' '-y' 'add-mcp' 'next-devtools-mcp@latest'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

coding-agentsmcpmcp-servernext-devtoolsnextjs

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

11 of 11 tools

Documented tools (11)

From project documentation. A server handshake does not verify each tool’s description or behavior.

browser_eval

Gateway. Point the agent at the agent-browser CLI for browser automation.

get_errors

current build, runtime, and type errors

get_logs

path to the dev log file (browser console + server output)

get_page_metadata

routes, pages, component metadata

get_project_metadata

project structure, config, dev server URL

get_server_action_by_id

resolve a Server Action ID to its source file

nextjs_call

Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).

nextjs_docs

Gateway. Point the agent at version-accurate docs in nodemodules/next/dist/docs/.

nextjs_index

Discover running Next.js dev servers and list each one's runtime MCP tools.

port

(required) — dev server port

toolName

(required) — runtime tool to invoke

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Next Devtools MCP Server

How do I connect Next Devtools MCP Server to Claude?: Run `claude mcp add next-devtools-mcp -- npx -y add-mcp next-devtools-mcp@latest` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Next Devtools MCP Server free?: MCPVault has not verified a licence for this server. Check the upstream terms and pricing before use; connected APIs may require a paid account.
What can Next Devtools MCP Server do?: Next Devtools MCP Server documents 11 tools to the agent, including browser_eval, get_errors, get_logs. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.