English Français العربية

Npm

Official registry Security

npm MCP — wraps the npm Registry API (free, no auth)

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http npm 'https://gateway.pipeworx.io/npm/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "npm": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/npm/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-npm
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-npm

npm MCP — wraps the npm Registry API (free, no auth)

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
search_packagesSearch npm for packages by keyword. Returns package names, descriptions, latest versions, publish dates, and publishers. Use when discovering libraries for a task.
get_packageGet full details for a specific package: version, description, dependencies, homepage, repository, and license. Use after search_packages to evaluate a candidate package.
get_downloadsFetch npm download counts for a package over a named period (last-day, last-week, last-month, last-year) or a custom date range like "2024-01-01:2024-06-30". Returns total downloads, start date, and end date.
list_versionsList published versions of an npm package with publish dates, dist-tags (latest/next/beta), and deprecation notices — answers "what versions of <pkg> exist", "when was <pkg> last published", "is the latest version deprecated". Returns versions newest-first, plus the package created/last-modified timestamps.
get_version_infoGet metadata for a SPECIFIC version (or dist-tag) of an npm package: dependencies, dev/peer dependencies, engines, license, tarball + integrity hash + unpacked size, and any deprecation notice. Use for "dependencies of <pkg>@<version>", pinned-version audits, or inspecting a particular release. Version accepts an exact version (e.g. "4.18.2"), a dist-tag (e.g. "latest", "next"), or omit for the latest.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "npm": {
      "url": "https://gateway.pipeworx.io/npm/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/npm/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.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/npm_search_packages \
  -H 'Content-Type: application/json' \
  -d '{"query":"http server framework"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/npm_search_packages. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "npm": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-npm"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-npm

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.

Using with ask_pipeworx

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 Npm data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Npm?

npm MCP — wraps the npm Registry API (free, no auth)

How do I install Npm?

It runs as a remote server. In Claude Code: claude mcp add --transport http npm 'https://gateway.pipeworx.io/npm/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Npm need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Npm open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Npm?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.