# Npm AI integration on Definable

> npm is the default package manager for JavaScript and Node.js, facilitating the sharing and reuse of code, managing dependencies, and streamlining project workflows.

## What this connects

npm is the default package manager for JavaScript and Node.js, facilitating the sharing and reuse of code, managing dependencies, and streamlining project workflows.

Vendor: https://www.npmjs.com/

## Tools available

**12** tools available. First 12:

- `NPM_DELETE_USER_TOKEN_LEGACY` — Delete User Token (Legacy) — Tool to delete a user authentication token using the legacy endpoint. Use when you need to revoke or remove a specific token from the npm registry.
- `NPM_GET_ALL_PACKAGES_DOWNLOAD_POINT` — Get All Packages Download Count Point — Get total npm registry download statistics for all packages for a specified time period. Returns aggregate download counts across the entire npm registry with start/end dates. Supports preset periods (last-day, last-week, last-month, last-year) or custom date ranges (YYYY-MM-DD:YYYY-MM-DD).
- `NPM_GET_DOWNLOAD_COUNTS_POINT` — Get NPM Download Counts Point — Get npm package download statistics for a specified time period. Returns total download counts with start/end dates for single packages, scoped packages, or bulk queries (up to 128 packages). Supports preset periods (last-day, last-week, last-month, last-year) or custom date ranges (YYYY-MM-DD:YYYY-MM-DD).
- `NPM_GET_DOWNLOAD_COUNTS_RANGE_PACKAGE` — Get NPM Package Download Counts Over Date Range — Tool to get download counts for an npm package over a specified date range. Use when you need historical daily download data.
- `NPM_GET_DOWNLOAD_RANGE_ALL` — Get All NPM Packages Download Counts by Period — Tool to get daily download counts for all npm packages over a specified period. Use when you need aggregate download statistics across the entire npm registry.
- `NPM_GET_REGISTRY_CHANGES` — Get Registry Changes Feed — Tool to get a stream of registry changes for replication purposes. Returns CouchDB-style change feed for following registry updates.
- `NPM_GET_REGISTRY_META` — Get NPM Registry Meta — Retrieves npm registry metadata via meta endpoints. Use 'ping' to verify registry connectivity or 'whoami' to get the authenticated username.
- `NPM_GET_VERSION_DOWNLOADS` — Get NPM Package Version Downloads (Last 7 Days) — Tool to get download counts for specific versions of a package over the last 7 days. Use when you need to understand which versions are most popular.
- `NPM_QUERY_BULK_SECURITY_ADVISORIES` — Query Bulk Security Advisories — Tool to bulk query security advisories for multiple npm packages. Use when you need to check vulnerability information for multiple packages and versions at once.
- `NPM_REGISTRY_GET_PACKAGE` — Get NPM Package Metadata — Tool to fetch metadata for a specified npm package. Use after confirming the exact package name, including scope. Responses can be large; prefer reading top-level fields like 'dist-tags', 'description', and 'license' rather than scanning the entire object.
- `NPM_REGISTRY_GET_ROOT` — Get NPM Registry Root Metadata — Fetches npm registry root metadata including total package count and update sequence. Returns database statistics from the npm replication service. No parameters required. Use this to get current registry statistics like the total number of packages available.
- `NPM_REGISTRY_SEARCH_PACKAGES` — Search NPM Packages — Tool to search for packages in the npm registry. Use when you need to find packages matching a search term. Results are returned in an 'objects' array; each element contains package metadata under a 'package' field and weekly download estimates under 'downloads.weekly'.

## Auth

Auth schemes: `API_KEY`.

## How agents use Npm

Inside a Definable workflow, Npm is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Npm** — the Researcher (GPT-5.5) pulls context from Npm (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Npm** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Npm (create record, post message, draft email).
- **Designer / Engineer → Distributor → Npm** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Npm (attach file, open PR comment, post status).

The Verifier checks every Npm call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/npm/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt