@pipeworx/packagephobia

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/packagephobia’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 1

Packagephobia MCP — measures the size an npm package takes up on disk after install (publish-size + install-size including all transitive deps). Complements bundlephobia, which measures runtime bundle size. Keyless.

Tools

• size(package, version?) — install + publish size for an npm package

Why bother?

Bundle size ≠ install size. A package can be tiny at runtime but pull in heavy dev/transitive deps that slow CI cache hydration. packagephobia measures the full node_modules footprint.

Data source

https://packagephobia.com/v2/api.json?p=<pkg>[@version]

Tools

• size — Return the publish size and full install size (including dependencies) in bytes for an npm package name and optional version via packagephobia.com.