Can Lyro publish a package or push a version through this integration?

No. The toolkit is read-only against the registry apart from a single write, Delete User Token (Legacy), which revokes an npm authentication token. Publishing, deprecating, and version promotion stay in your own release tooling.

Does Lyro need an authenticated npm token to answer download questions?

Not for most of them. Download counts, package metadata, search, and registry statistics come from public endpoints. A token is only needed for the authenticated calls: the whoami mode of Get NPM Registry Meta and Delete User Token (Legacy).

How many packages can Lyro check in one request?

Get NPM Download Counts Point accepts bulk queries of up to 128 packages at a time, and Query Bulk Security Advisories takes multiple packages and versions in a single call, so an audit of a dependency list does not turn into one request per entry.

Does it handle scoped packages such as @scope/name?

Yes. Get NPM Download Counts Point covers scoped packages alongside unscoped and bulk queries. Get NPM Package Metadata needs the exact name including the scope, so Lyro confirms the full name through Search NPM Packages before fetching it.

Npm MCP integration

Searches the registry, reads package metadata and dist-tags, pulls download counts by version or date range, and bulk-checks security advisories.

Connect Npm See all integrations

12actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get npm download counts point
Lyro retrieves download statistics for an npm package over a time period. Development teams monitor adoption rates and spot trends without querying npm directly.
Search npm packages
Lyro finds packages in the npm registry by name or keyword. Developers discover dependencies without leaving your support or automation platform.
Query bulk security advisories
Lyro checks multiple npm packages against security advisories in one call. Your team quickly spots vulnerable dependencies before they cause breaches.

See all 12 actions

How businesses use Npm + Lyro

Each card is one request a support team gets, and the Npm actions Lyro runs to close it.

Identify the right package and read what it actually ships
Lyro searches the registry for a term, then returns the matching package's dist-tags, description, and license rather than making someone open the registry page to check.
Search NPM PackagesGet NPM Package MetadataGet NPM Registry Meta
Answer adoption questions with real download numbers
Lyro reports downloads for a preset period, over a specific date range, or split by version across the last seven days, so a claim about how widely a package is used comes with the count behind it.
Get NPM Download Counts PointGet Package Downloads Over RangeGet Package Version Downloads
Screen a dependency list for known advisories
Lyro bulk-queries security advisories for a set of packages and versions in one call, then reads the metadata of anything flagged to confirm which release lines are affected.
Query Bulk Security AdvisoriesGet NPM Package MetadataGet Package Version Downloads
Track the registry itself, not just one package
Lyro pulls registry-wide totals, daily aggregate downloads across every package, and the replication change feed when the question is about ecosystem scale rather than a single dependency.
Get NPM Registry Root MetadataGet All Packages Downloads By PeriodGet Registry Changes Feed

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Npm actions it has and picks the ones a request needs.

01
Connect Npm
Authorize the Npm account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Npm actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Npm · Lyro

Everything else about Npm

Setup, permissions, and the limits of what Lyro can do inside Npm.

No. The toolkit is read-only against the registry apart from a single write, Delete User Token (Legacy), which revokes an npm authentication token. Publishing, deprecating, and version promotion stay in your own release tooling.

Every action available in Npm

All 12 actions your agent can call on Npm, straight from the live MCP connection.

Delete user token (legacy)
Delete a user authentication token using the legacy endpoint.
Get all packages download count point
Get total npm registry download statistics for all packages for a specified time period.
Get npm download counts point
Get npm package download statistics for a specified time period.
Get npm package download counts over date range
Get download counts for an npm package over a specified date range.
Get all npm packages download counts by period
Get daily download counts for all npm packages over a specified period.
Get registry changes feed
Get a stream of registry changes for replication purposes.
Get npm registry meta
Retrieves npm registry metadata via meta endpoints.
Get npm package version downloads (last 7 days)
Get download counts for specific versions of a package over the last 7 days.
Query bulk security advisories
Bulk query security advisories for multiple npm packages.
Get npm package metadata
Fetch metadata for a specified npm package.
Get npm registry root metadata
Fetches npm registry root metadata including total package count and update sequence.
Search npm packages
Search for packages in the npm registry.