Alimenter votre agent
L'URL propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/packagephobia/mcpLe bouton Claude ci-dessus ouvre Claude avec le nom et l'URL préremplis. Il vous reste à confirmer sur place.
claude mcp add --transport http io.github.pipeworx-io-packagephobia https://gateway.pipeworx.io/packagephobia/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-packagephobia": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/packagephobia/mcp" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
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.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Packagephobia MCP — install-size analysis for npm packages
size(package, version?) — install + publish size for an npm packageBundle 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.
https://packagephobia.com/v2/api.json?p=<pkg>[@version]
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"packagephobia": {
"url": "https://gateway.pipeworx.io/packagephobia/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/packagephobia/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 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/packagephobia_size \
-H 'Content-Type: application/json' \
-d '{"package":"react"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/packagephobia_size. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"packagephobia": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-packagephobia"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-packagephobia
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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 Packagephobia data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
Packagephobia MCP — install-size analysis for npm packages
{ "mcpServers": { "io.github.pipeworx-io-packagephobia": { "url": "https://gateway.pipeworx.io/packagephobia/mcp", "headers": {} } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration http pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
L'éditeur indique ces variables d'environnement : PIPEWORX_API_KEY.
Packagephobia est accessible via HTTP.
Dernière vérification : 2026-11-11. Packagephobia MCP — install-size analysis for npm packages