Hosting

Local

Transport

stdio (client launcher); local Next.js development server MCP endpoint at `/_next/mcp`

Endpoint

Local process; no hosted endpoint documented

Authentication

No authentication documented for local development-server access.

Requirements

• Next.js 16 or later in the project being inspected
• Node/npm tooling and a running Next.js development server
• Add `next-devtools-mcp` to the MCP-capable coding client

Setup steps

1. Add the documented project-root `.mcp.json` entry using command `npx` and args `-y`, `next-devtools-mcp@latest`, or run the official `npx add-mcp next-devtools-mcp@latest` setup command.
2. Start the project with its normal development command (for example `npm run dev`).
3. The devtools launcher discovers the running local Next.js server; keep the development server running while querying runtime tools.
4. Reload the MCP client if it was already open before adding configuration. Verify using `get_project_metadata` or `get_errors`.

The current outer server registers four tools: nextjs_index, nextjs_call, nextjs_docs and browser_eval. The dev server exposes runtime tools through nextjs_call; the additional stored runtime names are documented examples that depend on Next.js version, project state and instrumentation.

• nextjs_index

  Discover running Next.js development servers and their runtime tools.

  01
• nextjs_call

  Call a runtime tool on a discovered Next.js dev server.

  02
• nextjs_docs

  Direct the agent to version-matched local Next.js documentation.

  03
• browser_eval

  Direct the agent to browser tooling for page verification.

  04
• get_errors

  Retrieve current build, runtime, and type errors from the dev server.

  05
• get_logs

  Get the development log file path.

  06
• get_page_metadata

  Retrieve metadata about a page currently open in a browser.

  07
• get_project_metadata

  Retrieve project path and dev server URL.

  08
• get_routes

  List routes discovered from the project filesystem.

  09
• get_server_action_by_id

  Look up a Server Action ID and its source.

  10
• get_compilation_issues

  Report compilation issues across routes; Turbopack only.

  11
• compile_route

  Compile a route and report issues without requesting it; Turbopack only.

  12
• get_request_insights

  Return recorded request timeline/fetch/cache insights when experimental request insights is enabled.

  13

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Requires Next.js 16+ for the built-in `/_next/mcp` endpoint.
• Runtime metadata tools may require the page open in a browser; compilation tools have documented Turbopack constraints.
• Only connects to local development servers; it is not a hosted production monitoring service.
• The runtime tool set evolves by Next.js version.

• official tool reference

  Current next-devtools-mcp has four outer gateway tools. Runtime capabilities are discovered from a running Next.js dev server and change by framework version, project state and enabled instrumentation; the additional stored names are runtime examples, not separately registered top-level tools.

• official documentation or source

  Current next-devtools-mcp has four outer gateway tools. Runtime capabilities are discovered from a running Next.js dev server and change by framework version, project state and enabled instrumentation; the additional stored names are runtime examples, not separately registered top-level tools.

Documentation checked 2026-10-28T12:38:00.000Z. Connection has not been runtime tested.