Provides tools for analyzing npm package bundle sizes, including minified and gzipped sizes, tree-shakeability, dependencies, historical comparisons, and finding similar packages.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-bundlephobia check the bundle size of lodash"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bundlephobia MCP — bundle-size analysis for npm packages. Reports minified + gzipped size, tree-shakeability, dependency count, build time estimates. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
size(package, version?) — bundle size for package (or package@version)
similar(package, version?) — packages with similar functionality + their sizes
history(package, version?) — size history across versions (heuristic: queries each version)
recent_searches() — what other people have been measuring
Related MCP server: mcp-server-npm-plus
Bundlephobia is rate-limited and sometimes slow on first request (it builds + measures the package on demand). Subsequent requests for the same package@version are cached.
https://bundlephobia.com/api/
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bundlephobia": {
"url": "https://gateway.pipeworx.io/bundlephobia/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/bundlephobia/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bundlephobia data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Packagephobia MCP — install-size analysis for npm packages
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups