MCP server for analyzing Next.js build artifacts, route bundle footprint, and shared chunks
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
compare_buildsCompare two loaded Next.js builds and show which routes and chunks grew or shrank the most.Compare two loaded Next.js builds and show which routes and chunks grew or shrank the most.
No input schema was published for this tool.
explain_growthIdentify which routes and chunks are responsible for bundle size growth between two loaded builds.Identify which routes and chunks are responsible for bundle size growth between two loaded builds.
No input schema was published for this tool.
explain_shared_chunksShow which npm packages and app code dominate the shared chunks loaded by many routes, to identifyShow which npm packages and app code dominate the shared chunks loaded by many routes, to identify
No input schema was published for this tool.
find_duplicatesFind npm packages whose code is bundled into more than one chunk, wasting bytes, ranked by wastedFind npm packages whose code is bundled into more than one chunk, wasting bytes, ranked by wasted
No input schema was published for this tool.
get_largest_routesRank the heaviest user-facing routes in a loaded Next.js build by emitted chunk bytes.Rank the heaviest user-facing routes in a loaded Next.js build by emitted chunk bytes.
No input schema was published for this tool.
get_shared_chunksRank the heaviest shared chunks in a loaded Next.js build and show which routes depend on them.Rank the heaviest shared chunks in a loaded Next.js build and show which routes depend on them.
No input schema was published for this tool.
how_to_collect_statsExplain how to generate the webpack stats file (.next/stats.json) required by the bundle attributionExplain how to generate the webpack stats file (.next/stats.json) required by the bundle attribution
No input schema was published for this tool.
load_build_statsParse a Next.js .next directory and load route and chunk footprint data for later analysis.Parse a Next.js .next directory and load route and chunk footprint data for later analysis.
No input schema was published for this tool.
load_webpack_statsParse the webpack module stats file (.next/stats.json) and link it to a build loaded withParse the webpack module stats file (.next/stats.json) and link it to a build loaded with
No input schema was published for this tool.
suggest_optimizationsAggregate route, chunk, and (when loaded) webpack-stats evidence into severity-ranked,Aggregate route, chunk, and (when loaded) webpack-stats evidence into severity-ranked,
No input schema was published for this tool.
trace_importExplain why a module is bundled by tracing its import chain from an entry point to the module.Explain why a module is bundled by tracing its import chain from an entry point to the module.
No input schema was published for this tool.
11 of 11 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for analyzing Next.js build artifacts, route bundle footprint, and shared chunks
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.