developer-tools Static interface comparison

Next.js DevTools MCP

0.3.10 0.4.0

REVIEWPending human review

2 schema changes require review.No new authority detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools7 → 4
Added0
Removed3
Schema changes2
Input schema changes2
Output schema changes0
Unclassified schema changes0
Description changes3
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

6 tools with recorded changes

  1. browser_evalModifiedSchemaDescriptionREVIEWINFO

    What changed

    • browser_eval — Schema change: input property added: task.
    • browser_eval — Schema change: input property removed: action.
    • browser_eval — Schema change: input property removed: browser.
    • browser_eval — Schema change: input property removed: button.
    • browser_eval — Schema change: input property removed: doubleClick.
    • browser_eval — Schema change: input property removed: element.
    • browser_eval — Schema change: input property removed: endElement.
    • browser_eval — Schema change: input property removed: endRef.
    • browser_eval — Schema change: input property removed: errorsOnly.
    • browser_eval — Schema change: input property removed: fields.
    • browser_eval — Schema change: input property removed: files.
    • browser_eval — Schema change: input property removed: fullPage.
    • browser_eval — Schema change: input property removed: headless.
    • browser_eval — Schema change: input property removed: modifiers.
    • browser_eval — Schema change: input property removed: ref.
    • browser_eval — Schema change: input property removed: script.
    • browser_eval — Schema change: input property removed: startElement.
    • browser_eval — Schema change: input property removed: startRef.
    • browser_eval — Schema change: input property removed: text.
    • browser_eval — Schema change: input property removed: url.
    • browser_eval: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousAutomate and test web applications using Playwright browser automation. This tool connects to playwright-mcp server and provides access to all Playwright capabilities. CRITICAL FOR PAGE VERIFICATION: When verifying pages in Next.js projects (especially during upgrades or testing), you MUST use browser automation to load pages in a real browser instead of curl or simple HTTP requests. This is because: - Browser automation actually renders the page and executes JavaScript (curl only fetches HTML) - Detects runtime errors, hydration issues, and client-side problems that curl cannot catch - Verifies the full user experience, not just HTTP status codes - Captures browser console errors and warnings via console_messages action IMPORTANT FOR NEXT.JS PROJECTS: If working with a Next.js application, PRIORITIZE using the 'nextjs_index' and 'nextjs_call' tools instead of browser console log forwarding. Next.js has built-in MCP integration that provides superior error reporting, build diagnostics, and runtime information directly from the Next.js dev server. Only use browser_eval's console_messages action as a fallback when these Next.js tools are not available or when you specifically need to test client-side browser behavior that Next.js runtime cannot capture. Available actions: - start: Start browser automation (automatically installs if needed). Verbose logging is always enabled. - navigate: Navigate to a URL - click: Click on an element - type: Type text into an element - fill_form: Fill multiple form fields at once - evaluate: Execute JavaScript in browser context - screenshot: Take a screenshot of the page - console_messages: Get browser console messages (for Next.js, prefer nextjs_index/nextjs_call tools instead) - close: Close the browser - drag: Perform drag and drop - upload_file: Upload files - list_tools: List all available browser automation tools from the server Note: The playwright-mcp server will be automatically installed if not present.
    CurrentSet up and use browser automation for this project via the agent-browser CLI. This tool does NOT drive the browser itself. It points you at `agent-browser` — a fast, native browser-automation CLI built for agents (https://github.com/vercel-labs/agent-browser) — and tells you how to install it (if needed) and where to start. You then run its commands directly (you have shell access), which is faster and more capable than proxying automation through MCP. Call this when you need to open pages, click, type, screenshot, or capture console errors in a real browser.

    Input schema

    PropertyPrevious (0.3.10)Current (0.4.0)Change
    actionstring, enum (12)optionalnot present
    • Removed
    browserstring, enum (4)optionalnot present
    • Removed
    buttonstring, enum (3)optionalnot present
    • Removed
    doubleClickbooleanoptionalnot present
    • Removed
    elementstringoptionalnot present
    • Removed
    endElementstringoptionalnot present
    • Removed
    endRefstringoptionalnot present
    • Removed
    errorsOnlybooleanoptionalnot present
    • Removed
    fieldsarrayoptionalnot present
    • Removed
    fields › [items]objectnot present
    • Removed
    fields › [items] › selectorstringoptionalnot present
    • Removed
    fields › [items] › valuestringoptionalnot present
    • Removed
    filesarrayoptionalnot present
    • Removed
    files › [items]stringnot present
    • Removed
    fullPagebooleanoptionalnot present
    • Removed
    headlessbooleanoptionalnot present
    • Removed
    modifiersarrayoptionalnot present
    • Removed
    modifiers › [items]stringnot present
    • Removed
    refstringoptionalnot present
    • Removed
    scriptstringoptionalnot present
    • Removed
    startElementstringoptionalnot present
    • Removed
    startRefstringoptionalnot present
    • Removed
    tasknot presentstringoptional
    • Added
    textstringoptionalnot present
    • Removed
    urlstringoptionalnot present
    • Removed
    1 unchanged entry
    • (schema root)

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. enable_cache_componentsRemovedRemovedREVIEW

    What changed

    • Tool enable_cache_components was removed.

    Why it could matter

    • Integrations, prompts or agent configurations that call this tool will not find it in this release.

    What to verify

    • Check whether existing integrations still reference this tool.
    Declared effect
    unknown → —

    Input schema

    PropertyPrevious (0.3.10)Current (0.4.0)Change
    (schema root)objectnot present
    • Removed
    project_pathstringoptionalnot present
    • Removed

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. initRemovedRemovedREVIEW

    What changed

    • Tool init was removed.

    Why it could matter

    • Integrations, prompts or agent configurations that call this tool will not find it in this release.

    What to verify

    • Check whether existing integrations still reference this tool.
    Declared effect
    unknown → —

    Input schema

    PropertyPrevious (0.3.10)Current (0.4.0)Change
    (schema root)objectnot present
    • Removed
    project_pathstringoptionalnot present
    • Removed

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. nextjs_docsModifiedSchemaDescriptionREVIEWINFO

    What changed

    • nextjs_docs — Schema change: input property added: project_path.
    • nextjs_docs — Schema change: input property added: topic.
    • nextjs_docs — Schema change: input property removed: anchor.
    • nextjs_docs — Schema change: input property removed: path.
    • nextjs_docs: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousFetch Next.js official documentation by path. IMPORTANT: You MUST first read the `nextjs-docs://llms-index` MCP resource to get the correct path. Do NOT guess paths. Workflow: 1. Read the `nextjs-docs://llms-index` resource to get the documentation index 2. Find the relevant path in the index for what you're looking for 3. Call this tool with that exact path Example: nextjs_docs({ path: "/docs/app/api-reference/functions/refresh" })
    CurrentFind the version-accurate Next.js documentation for THIS project. This tool does NOT fetch documentation. Next.js 16+ ships its full docs inside the installed package at `node_modules/next/dist/docs/` (markdown), kept in sync with the exact version you have installed. This tool tells you where those docs are and how to read them — so you read the docs that match this project, not a generic or outdated copy. Call this before answering Next.js questions or writing Next.js code. Then read the relevant guide from the path it returns. If the project is on an older Next.js, it will tell you how to upgrade.

    Input schema

    PropertyPrevious (0.3.10)Current (0.4.0)Change
    anchorstringoptionalnot present
    • Removed
    pathstringoptionalnot present
    • Removed
    project_pathnot presentstringoptional
    • Added
    topicnot presentstringoptional
    • Added
    1 unchanged entry
    • (schema root)

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  5. nextjs_indexModifiedDescriptionINFO

    What changed

    • nextjs_index: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousDiscover all running Next.js development servers and list their available MCP tools. WHEN TO USE THIS TOOL - Use proactively in these scenarios: 1. **Before implementing ANY changes to the app**: When asked to add, modify, or fix anything in the application: - "Add a loading state" → Check current component structure and routes first - "Fix the navigation" → Inspect existing routes and components - "Update the API endpoint" → Query current routes and data flows - "Add error handling" → Check runtime errors and component hierarchy - "Refactor the auth logic" → Inspect current auth implementation and routes - "Optimize performance" → Check runtime diagnostics and component tree Use this to understand where changes should be made and what currently exists. 2. **For diagnostic and investigation questions**: - "What's happening?" / "What's going on?" / "Why isn't this working?" - "Check the errors" / "See what's wrong" - "What routes are available?" / "Show me the routes" - "Clear the cache" / "Reset everything" - Questions about build status, compilation errors, or runtime diagnostics 3. **For agentic codebase search**: Use this as FIRST CHOICE for searching the currently running app. If not found, fallback to static codebase search tools. KEY PRINCIPLE: If the request involves the running Next.js application (whether to investigate OR modify it), query the runtime FIRST to understand current state before proceeding. REQUIREMENTS: - Next.js 16 or later (MCP support was added in v16) - If you're on Next.js 15 or earlier, use the 'upgrade-nextjs-16' MCP prompt to upgrade first Next.js 16+ exposes an MCP (Model Context Protocol) endpoint at /_next/mcp automatically when the dev server starts. No configuration needed - MCP is enabled by default in Next.js 16 and later. This tool discovers all running Next.js servers and returns: - Server port, PID, and URL - Complete list of available MCP tools for each server - Tool descriptions and input schemas After calling this tool, use 'nextjs_call' to execute specific tools. [IMPORTANT] If auto-discovery returns no servers: 1. Ask the user which port their Next.js dev server is running on 2. Call this tool again with the 'port' parameter set to the user-provided port If the MCP endpoint is not available: 1. Ensure you're running Next.js 16 or later (use the 'upgrade-nextjs-16' prompt to upgrade) 2. Verify the dev server is running (npm run dev) 3. Check that the dev server started successfully without errors
    CurrentDiscover all running Next.js development servers and list their available MCP tools. WHEN TO USE THIS TOOL - Use proactively in these scenarios: 1. **Before implementing ANY changes to the app**: When asked to add, modify, or fix anything in the application: - "Add a loading state" → Check current component structure and routes first - "Fix the navigation" → Inspect existing routes and components - "Update the API endpoint" → Query current routes and data flows - "Add error handling" → Check runtime errors and component hierarchy - "Refactor the auth logic" → Inspect current auth implementation and routes - "Optimize performance" → Check runtime diagnostics and component tree Use this to understand where changes should be made and what currently exists. 2. **For diagnostic and investigation questions**: - "What's happening?" / "What's going on?" / "Why isn't this working?" - "Check the errors" / "See what's wrong" - "What routes are available?" / "Show me the routes" - "Clear the cache" / "Reset everything" - Questions about build status, compilation errors, or runtime diagnostics 3. **For agentic codebase search**: Use this as FIRST CHOICE for searching the currently running app. If not found, fallback to static codebase search tools. KEY PRINCIPLE: If the request involves the running Next.js application (whether to investigate OR modify it), query the runtime FIRST to understand current state before proceeding. REQUIREMENTS: - Next.js 16 or later (MCP support was added in v16) - If you're on Next.js 15 or earlier, upgrade first by running 'npx @next/codemod@latest upgrade latest' Next.js 16+ exposes an MCP (Model Context Protocol) endpoint at /_next/mcp automatically when the dev server starts. No configuration needed - MCP is enabled by default in Next.js 16 and later. This tool discovers all running Next.js servers and returns: - Server port, PID, and URL - Complete list of available MCP tools for each server - Tool descriptions and input schemas After calling this tool, use 'nextjs_call' to execute specific tools. [IMPORTANT] If auto-discovery returns no servers: 1. Ask the user which port their Next.js dev server is running on 2. Call this tool again with the 'port' parameter set to the user-provided port If the MCP endpoint is not available: 1. Ensure you're running Next.js 16 or later (upgrade with 'npx @next/codemod@latest upgrade latest') 2. Verify the dev server is running (npm run dev) 3. Check that the dev server started successfully without errors

    Input schema

    Input schema unchanged.

    2 unchanged entries
    • (schema root)
    • port

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  6. upgrade_nextjs_16RemovedRemovedREVIEW

    What changed

    • Tool upgrade_nextjs_16 was removed.

    Why it could matter

    • Integrations, prompts or agent configurations that call this tool will not find it in this release.

    What to verify

    • Check whether existing integrations still reference this tool.
    Declared effect
    unknown → —

    Input schema

    PropertyPrevious (0.3.10)Current (0.4.0)Change
    (schema root)objectnot present
    • Removed
    project_pathstringoptionalnot present
    • Removed

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
1 tool with no recorded change
  • nextjs_call

Evidence and provenance

Static findings
REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Pending human review. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
next-devtools/0.3.10~0.4.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 15, 2026, 3:20 AM UTC.
Distribution
npm
Previous release
next-devtools-mcp@0.3.107 tools · published by the registry Jan 8, 2026, 8:55 PM UTCArtifact integritysha512-r7SvHCiS6glEuN98x0HpW+RMbRNaTO7ni8cR+GO1Ww4P83IIwDgKUDdRwvvwtk5WXf4wiq6Qd1xDCvsTm9oDSw==Interface fingerprintsha256:f8ba37299ad1492ee247fd7bb3f19f8bac7067050425313b10b7389d92325458Exact interface snapshot (JSON)
Current release
next-devtools-mcp@0.4.04 tools · published by the registry Jun 24, 2026, 10:47 PM UTCArtifact integritysha512-PTIoi+TihyztSTPkl+YIesL81wU3pRDo6QCg1wgjvLGfBlXv3yamvQyoI8j/I2t7gqDStXoa7jtn/YUdvcBQuw==Interface fingerprintsha256:0cf55308e1e3eb491577eb63f482bbc78dba2e13ac84d00e93fc34b4fa7dda16Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 15, 2026

Requires review

5 findings
  • enable_cache_componentsREVIEWRemoved

    Capability removed; a workflow may depend on it

    Authority
    UNKNOWN—
  • initREVIEWRemoved

    Capability removed; a workflow may depend on it

    Authority
    UNKNOWN—
  • upgrade_nextjs_16REVIEWRemoved

    Capability removed; a workflow may depend on it

    Authority
    UNKNOWN—
  • browser_evalREVIEWChanged

    Input schema changed

    Show details
    • input property added: task
    • input property removed: action
    • input property removed: browser
    • input property removed: button
    • input property removed: doubleClick
    • input property removed: element
    • input property removed: endElement
    • input property removed: endRef
    • input property removed: errorsOnly
    • input property removed: fields
    • input property removed: files
    • input property removed: fullPage
    • input property removed: headless
    • input property removed: modifiers
    • input property removed: ref
    • input property removed: script
    • input property removed: startElement
    • input property removed: startRef
    • input property removed: text
    • input property removed: url
    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • nextjs_docsREVIEWChanged

    Input schema changed

    Show details
    • input property added: project_path
    • input property added: topic
    • input property removed: anchor
    • input property removed: path
    Authority
    UNKNOWNUNKNOWN
    Authority unchanged

Informational

3 findings
  • browser_evalINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • nextjs_docsINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • nextjs_indexINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to Next.js DevTools MCP release history