list_npm_files

Pack: jsdelivr · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/list_npm_files for the schema, then POST the same URL with its arguments for the data.

jsDelivr Data API — the file tree of one published npm package version (latest by default) as jsDelivr indexes it for CDN delivery. Returns the directory structure with each file’s path, byte size, content hash and type, read from jsDelivr’s package index. Answers which files, entry points and build outputs an npm package version actually ships.

Parameters

Example call

Arguments

{
  "package_name": "lodash"
}

curl

curl -X POST https://gateway.pipeworx.io/jsdelivr/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_npm_files","arguments":{"package_name":"lodash"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('list_npm_files', {
  "package_name": "lodash"
});

More examples

{
  "package_name": "next",
  "version": "14.0.0"
}

{
  "package_name": "@types/node",
  "version": "22.0.0"
}

Response shape

{
  "type": "object",
  "description": "List of files in a published npm package version"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "jsdelivr": {
      "url": "https://gateway.pipeworx.io/jsdelivr/mcp"
    }
  }
}

See Getting Started for client-specific install steps.