Npm
MCP server for npm package management — publish, version, search, audit, and more
npm-mcp
MCP server that lets AI assistants manage npm packages. Publish, version, search, audit, install, and more -- all through Claude Code or any MCP client.
The MCP server requires Node.js 20 or newer. Individual npm CLI features may require a newer Node.js/npm combination as noted below.
When to Use
| Task | Tool |
|---|---|
| "Publish this package to npm" | publish |
| "Check for outdated dependencies" | outdated |
| "Run a security audit on my packages" | audit |
| "Search npm for authentication libraries" | search |
| "Bump the version and publish" | version then publish |
| "Check who owns this npm package" | owner |
| "View download stats for my package" | view |
For AI agents: See
llms.txtfor a machine-readable summary. Copytemplates/CLAUDE.mdortemplates/AGENTS.mdinto your project to teach your agent about this MCP.
Why
You're in Claude Code building a library. You finish the code, and now you need to publish it. Instead of switching to a terminal:
You: publish this package to npm with public access
Claude: [calls publish tool] Published @yourorg/lib@1.0.0 successfully
That's it. No context switching.
Setup
1. Install
git clone https://github.com/mikusnuz/npm-mcp.git
cd npm-mcp
npm install
npm run build
2. Get npm token
Go to npmjs.com > Account > Access Tokens and create a
granular access token with access to the packages you need. Classic and
Automation tokens are no longer supported. A stage-only token uses the stage
workflow below. Existing npm login credentials also work.
3. Add to Claude Code
Edit ~/.claude/settings.json:
{
"mcpServers": {
"npm-mcp": {
"command": "node",
"args": ["/path/to/npm-mcp/dist/index.js"],
"env": {
"NPM_TOKEN": "npm_xxxxxxxxxxxx"
}
}
}
}
Or if you've already run npm login locally, skip NPM_TOKEN -- it uses your ~/.npmrc automatically.
Tools
Publishing & Versioning
| Tool | Description |
|---|---|
publish |
Publish a package to npm registry |
stage |
Stage, list, inspect, download, approve, or reject a pending package version |
version |
Bump package version (patch/minor/major/pre*) |
unpublish |
Remove a package version |
deprecate |
Deprecate a version (or undeprecate with empty message) |
pack |
Preview what would be published |
Package Info
| Tool | Description |
|---|---|
view |
View package info from registry |
search |
Search npm registry |
bugs |
Get bug tracker URL for a package |
repo |
Get repository URL for a package |
docs |
Get documentation URL for a package |
diff |
Show diff between package versions |
Dependency Management
| Tool | Description |
|---|---|
install |
Install packages |
pending-scripts |
List unreviewed dependency install scripts without changing policy (npm 12+) |
approve-scripts |
Approve named, reviewed dependencies with version pinning (npm 12+) |
deny-scripts |
Deny install scripts for named dependencies across versions (npm 12+) |
uninstall |
Remove packages |
update |
Update packages to latest semver-compatible version |
outdated |
Check for outdated packages |
ls |
List installed packages |
explain |
Explain why a package is installed |
dedupe |
Reduce duplication in dependency tree |
prune |
Remove extraneous packages |
fund |
Show funding info for dependencies |
query |
Query packages using CSS-like selectors |
Security & Diagnostics
From the project's README.