Webpack MCP Server

If you already use Webpack, the webpack mcp server is the piece that lets your assistant work with it directly. Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap.

What the server does

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• bundleStatsFile — The bundleStatsFile tool exposed by this server
• bundleDir — The bundleDir tool exposed by this server
• options — Size definitions
• stat — This is the "input" size of your files, before any transformations like minification
• parsed — This is the "output" size of your files. If you're using a Webpack plugin such as Uglify, then this value will reflect the minified size of your code
• gzip — This is the size of running the parsed bundles/modules through gzip compression
• brotli — This is the size of running the parsed bundles/modules through Brotli compression
• zstd — This is the size of running the parsed bundles/modules through Zstandard compression. (Node.js 22.15.0+ is required for this feature)
• Sidebar — The Sidebar Menu can be opened by clicking the > button at the top left of the report. You can select or deselect chunks to display under the "Show

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Webpack.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Webpack's toolset — bundleStatsFile, bundleDir, options and 6 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.