Publish a package to the npm registry

Bump the package version

View package information from the registry

Search npm registry for packages

Remove a package version from the registry

Deprecate a version of a package

Manage package owners

Manage distribution tags

Create a tarball from a package (preview what would be published)

Check which npm user is currently authenticated. If not logged in, set NPM_TOKEN env var in MCP config.

Initialize a new package.json

Run a security audit on the package

Check for outdated packages in a project

List installed packages in a project

Install packages in a project

Remove packages from a project

Update packages in a project to their latest semver-compatible version

Set or view access level on published packages

Manage npm access tokens (list or revoke)

Check connectivity to the npm registry

Get the bug tracker URL for a package

Get the repository URL for a package

Get the documentation URL for a package

Show diff between package versions or between local and registry

Manage package.json fields programmatically

Show funding information for installed packages

Reduce duplication in the dependency tree

Explain why a package is installed (show dependency chain)

Generate a Software Bill of Materials (SBOM) for a project

View or modify npm user profile settings

Clean install dependencies from lockfile (for CI environments)

Run a script defined in package.json

Run diagnostics to check npm environment health

Manage the npm cache

View npm configuration (read-only for safety)

Remove extraneous packages not listed in package.json

Symlink a local package for development

Query installed packages using CSS-like selectors