About this integration
MCP server for npm package management — publish, version, search, audit, and more
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.2.1
- Package
- @mikusnuz/npm-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@mikusnuz/npm-mcpQualified from the pinned publisher README and npm manifest only. No npm command, package script, registry operation, or integration endpoint was executed; destructive capabilities retain the caller's npm permissions.
Capabilities: Publish and version npm packages, Inspect and search the npm registry, Manage project dependencies, Run npm audits and generate SBOMs, Manage npm access, owners, tags, and tokens
Connected profiles
Additional details
io.github.mikusnuz/npm
Source ↗ · Checked 2026-09-171.2.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@mikusnuz/npm-mcp
Source ↗ · Checked 2026-09-191.2.1
Source ↗ · Checked 2026-09-19Publisher configuration launches the built Node entrypoint as an MCP server with a preconfigured token or existing npm login.
Source ↗ · Checked 2026-09-19Authenticated npm operations use NPM_TOKEN or the token stored by an earlier npm login; this review classifies the documented NPM_TOKEN path as API-key credentials.
Source ↗ · Checked 2026-09-19The reviewed connection is a local Node process pointing to the package's dist/index.js entrypoint over the existing stdio listing transport.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19