MCP100 Assessment

Editorial verdict

Official Next.js development MCP integration that exposes runtime errors/state, route metadata, logs, documentation and upgrade/testing helpers to coding agents. Capabilities: Read build/runtime/type errors; Query live development state and route metadata; Inspect Server Actions/component hierarchy; Read development logs; Query Next.js knowledge/base documentation; Use migration/upgrade helpers; Integrate browser verification through Playwright MCP

Reviewed September 13, 2026

Task Fit

Mapped

Developer workflows

Trust

Status warning

maintenance_source_health; client_coverage; tool_contract; install_supply_chain; advisory_freshness; adoption_evidence_presence

Maintenance

Recheck needed

The source snapshot needs another refresh before maintenance can be interpreted.

Popularity

Signals unavailable

No independently comparable adoption metric is currently stored.

Best for

Next.js 16+ developers who want agents to inspect the live dev server and use first-party Next.js guidance.

Not ideal for

Users who need a broadly proven, low-risk, fully mature Selected-grade integration today.

Avoid if

Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.

Trade-offs

The tool surface is still actively expanding, so MCP-specific maturity and stability need more evidence.

Evidence scope

Evidence

Stale source snapshot - recheck needed

Popularity

No MCP-specific repository metric is stored

No MCP-specific package metric is stored

Stars observation date unavailable · Downloads observation date unavailable

No exact public repository is documented.

Exact package is documented; download evidence is unavailable.

Maintenance

Publisher activity observed September 13, 2026

Stale source snapshot - recheck needed

Trust review

Source relationship: First-party MCP

Reviewed September 13, 2026

Official setup docs ↗GitHub repository ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Transport not recorded

Publisher documented

`claude mcp add next-devtools npx next-devtools-mcp@latest`.

The publisher provides client-specific setup instructions.

Verify safely: Claude Code: `claude mcp list` and/or `/mcp` to confirm Connected; use any stronger vendor-documented smoke test where listed.

Uninstall and revoke

Claude Code: `claude mcp remove <name>`; also revoke OAuth/device/API credentials in the vendor account when the vendor provides such a control.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-09-20T00:00:00.000Z

Evidence 1 ↗

Loading optional publisher installation details…

Show source-catalog configuration

`claude mcp add next-devtools npx next-devtools-mcp@latest`.

Capability

What it does

Official Next.js development MCP integration that exposes runtime errors/state, route metadata, logs, documentation and upgrade/testing helpers to coding agents. Capabilities: Read build/runtime/type errors; Query live development state and route metadata; Inspect Server Actions/component hierarchy; Read development logs; Query Next.js knowledge/base documentation; Use migration/upgrade helpers; Integrate browser verification through Playwright MCP

Developer ToolsSoftware & Technology

Representative uses

Next.js 16+ developers who want agents to inspect the live dev server and use first-party Next.js guidance.

Important limits

Users who need a broadly proven, low-risk, fully mature Selected-grade integration today.

Context Footprint

Not measured yet

Estimated token footprint of the MCP tool schemas exposed to the agent.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Designed primarily for local development; no universal hosted authentication is implied by the integration.
Permissions: Exposes application development/runtime diagnostics to the agent; code changes occur through the coding agent rather than the built-in endpoint itself.
Data handling: Local app metadata, logs and errors are exposed to the connected AI client/provider.
Cost: Open-source framework tooling; model/provider and development infrastructure costs remain separate.
Risk and cautions: The tool surface is still actively expanding, so MCP-specific maturity and stability need more evidence.

Related reviewed MCPs

Other options

Context7 MCP

MCP100 Selected

Retrieve current library and framework documentation for coding agents.

Choose this instead if

Choose Context7 MCP instead if current library and API documentation inside coding agents.

Retrieve current library and framework documentation for coding agents.

Compare with Next.js DevTools View Context7 MCP details

Docker MCP Gateway

MCP100 Selected

Discover and run MCP servers through Docker's MCP gateway.

Choose this instead if

Choose Docker MCP Gateway instead if running multiple MCP servers behind one stdio connection.

Discover and run MCP servers through Docker's MCP gateway.

Compare with Next.js DevTools View Docker MCP Gateway details

GitHub MCP

MCP100 Selected

Work with repositories, issues, pull requests, and GitHub workflows.

Choose this instead if

Choose GitHub MCP instead if repository, issue, pull-request, and code context.

Work with repositories, issues, pull requests, and GitHub workflows.

Compare with Next.js DevTools View GitHub MCP details

Read publisher documentation

Publisher documentation

MCP100 source-backed summary

A concise MCP100 summary built from the reviewed publisher sources. It is not a publisher README; use the original link for the latest full documentation.

View original README ↗

Next.js DevTools

Official Next.js development MCP integration that exposes runtime errors/state, route metadata, logs, documentation and upgrade/testing helpers to coding agents. Capabilities: Read build/runtime/type errors; Query live development state and route metadata; Inspect Server Actions/component hierarchy; Read development logs; Query Next.js knowledge/base documentation; Use migration/upgrade helpers; Integrate browser verification through Playwright MCP

What it can help with

Next.js 16+ developers who want agents to inspect the live dev server and use first-party Next.js guidance.

Important limits

Users who need a broadly proven, low-risk, fully mature Selected-grade integration today.

Loading optional publisher documentation…

FAQ

Is this an official MCP?

io.github.vercel is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗