NPM Registry integration

Developer Tools & Infrastructure · 6 actions · API key auth

Access the npm registry to search packages, get package information, versions, dependencies, and download statistics

Put NPM Registry to work View NPM Registry integration docs

Overview

The ModuleX NPM Registry integration lets a ModuleX agent operate NPM Registry on your behalf — running find actions across package infos, packages and popular packages — directly from a plain-English request, using your organization's own NPM Registry credentials. No pre-built workflow is required: the agent picks the right NPM Registry action for the task.

NPM Registry is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right NPM Registry action — or, when you want a repeatable process, the composer assembles a NPM Registry workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive NPM Registry in plain English

Type what you want. A ModuleX agent picks the right NPM Registry action — or chains several — and runs it. No workflow to build.

Show me the package infos that match what I describe
resolves toget_package_info
Search for npm packages by keyword or name
resolves tosearch_packages
Get a list of popular npm packages sorted by popularity score
resolves toget_popular_packages

Use cases

What you can automate with NPM Registry

Look up a package info on demandget_package_info
Find the packages that match what you describesearch_packages
Get a list of popular npm packages sorted by popularity scoreget_popular_packages
Get all available versions of an npm package with publication dates and dist-tagsget_package_versions
Get the dependencies, devDependencies, and peerDependencies of an npm packageget_package_dependencies
Get download statistics for an npm package including total and daily download countsget_package_download_stats

At a glance

NPM Registry integration at a glance

VendorNPM Registry

CategoryDeveloper Tools & Infrastructure

Actions available6

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 6 NPM Registry actions

Package Infos1

get_package_info

Get detailed information about an npm package including name, version, description, author, homepage, repository, and dependencies

Packages1

search_packages

Search for npm packages by keyword or name

Popular Packages1

get_popular_packages

Get a list of popular npm packages sorted by popularity score

Package Versions1

get_package_versions

Get all available versions of an npm package with publication dates and dist-tags

Package Dependencies1

get_package_dependencies

Get the dependencies, devDependencies, and peerDependencies of an npm package

Package Download Stats1

get_package_download_stats

Get download statistics for an npm package including total and daily download counts

See full parameters and response schemas in the NPM Registry integration docs

Two ways

Two ways to use NPM Registry in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right NPM Registry action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires NPM Registry into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting NPM Registry

API keyNPM Registry uses API-key authentication. You provide your own NPM Registry secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use NPM Registry without re-authenticating.

Step-by-step setup in the NPM Registry docs

Pairs well with NPM Registry

Agents often chain NPM Registry with these — connect them once and the agent can use all of them in a single task.

FAQ

NPM Registry + ModuleX FAQ

A ModuleX agent can run any of NPM Registry's 6 actions — across package infos, packages, popular packages and package versions — from a plain-English request, using your organization's own NPM Registry credentials.

No. The agent selects the right NPM Registry action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own NPM Registry API key, stored encrypted and scoped to your organization.

6, spanning package infos, packages, popular packages and package versions.

NPM Registry runs on your own credentials, so any NPM Registry usage is billed by NPM Registry directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put NPM Registry to work in ModuleX.

Connect NPM Registry once with your own credentials and let your agent run all 6 actions on demand.

Put NPM Registry to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →