developer-tools Static interface comparison

Next.js DevTools MCP

0.3.9 0.3.10

REVIEWPending human review

1 schema change requires 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 → 7
Added0
Removed0
Schema changes1
Input schema changes1
Output schema changes0
Unclassified schema changes0
Description changes2
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

2 tools with recorded changes

  1. initModifiedDescriptionINFO

    What changed

    • init: 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
    Previous⚠️ CALL THIS FIRST - Initialize Next.js DevTools MCP context and establish MANDATORY documentation requirements. **IMPORTANT: This tool MUST be called at the START of every Next.js development session.** This tool fetches the latest Next.js documentation and establishes ABSOLUTE requirements for using the nextjs_docs tool for ALL Next.js-related queries. Key Points: - Fetches latest Next.js LLM documentation from nextjs.org - Establishes MANDATORY requirement to use nextjs_docs for ALL Next.js concepts - Instructs AI to forget any prior Next.js knowledge and always query docs - Documents all available MCP tools (nextjs_docs, nextjs_index, nextjs_call, browser_eval, upgrade_nextjs_16, enable_cache_components) Use this tool at the beginning of a Next.js session to: - Reset AI's Next.js knowledge baseline - Ensure 100% documentation-first approach with no exceptions - Understand available tools and their use cases - Follow best practices for Next.js development
    Current⚠️ CALL THIS FIRST - Initialize Next.js DevTools MCP context and establish MANDATORY documentation requirements. **IMPORTANT: This tool MUST be called at the START of every Next.js development session.** This tool: - Establishes MANDATORY requirement to use nextjs_docs for ALL Next.js-related queries - Instructs AI to forget any prior Next.js knowledge and always query docs - Documents all available MCP tools (nextjs_docs, nextjs_index, nextjs_call, browser_eval, upgrade_nextjs_16, enable_cache_components) Use this tool at the beginning of a Next.js session to: - Reset AI's Next.js knowledge baseline - Ensure 100% documentation-first approach with no exceptions - Understand available tools and their use cases - Follow best practices for Next.js development

    Input schema

    Input schema unchanged.

    2 unchanged entries
    • (schema root)
    • project_path

    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. nextjs_docsModifiedSchemaDescriptionREVIEWINFO

    What changed

    • nextjs_docs — Schema change: input property removed: action.
    • nextjs_docs — Schema change: input property removed: query.
    • nextjs_docs — Schema change: input property removed: routerType.
    • nextjs_docs — Schema change: input property path changed: +description="Documentation 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
    PreviousSearch and retrieve Next.js official documentation. Three actions: 1) 'get' - Fetch full docs with a path (preferred after init). 2) 'search' - Find docs by keyword (redirects to use llms.txt index if init was called). 3) 'force-search' - Bypass init check and force API search (escape hatch only). After calling init, prefer using 'get' directly with paths from the llms.txt index.
    CurrentFetch 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" })

    Input schema

    PropertyPrevious (0.3.9)Current (0.3.10)Change
    actionstring, enum (3)optionalnot present
    • Removed
    pathstringoptionalstringoptional
    • Description changed
    querystringoptionalnot present
    • Removed
    routerTypestringoptionalnot present
    • Removed
    2 unchanged entries
    • (schema root)
    • anchor

    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 tools with no recorded change
  • browser_eval
  • enable_cache_components
  • nextjs_call
  • nextjs_index
  • upgrade_nextjs_16

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.9~0.3.10The 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.97 tools · published by the registry Jan 6, 2026, 4:47 PM UTCArtifact integritysha512-9IKHjEMzJp9mn+tQN7+UfSyw/nhlnjTUIYQXmSaDujCGhXenLinHWFUEKylqJrsN+jAg5l7bJR+LaNnK2HWQJQ==Interface fingerprintsha256:e4679b6859cd2231c7500225a2347bc47d50da7d1095e76a977093ebc12d0a71Exact interface snapshot (JSON)
Current 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)

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

1 finding
  • nextjs_docsREVIEWChanged

    Input schema changed

    Show details
    • input property removed: action
    • input property removed: query
    • input property removed: routerType
    • input property path changed: +description="Documentation path…
    Authority
    UNKNOWNUNKNOWN
    Authority unchanged

Informational

2 findings
  • initINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • nextjs_docsINFOChanged

    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