MCP server: One MCP server.

Npm

@alisaittekeMCP server · External

MCP server for npm package management, security analysis, and compatibility checking

Vulnerability managementv0.0.3MITTypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

NPM MCP Banner
From the README · 1 of 2

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@alisaitteke/npm-mcpv0.0.3

Run

npx -y @alisaitteke/npm-mcp

MCP client config

{
  "mcpServers": {
    "npm": {
      "command": "npx",
      "args": [
        "-y",
        "@alisaitteke/npm-mcp"
      ]
    }
  }
}
README2 min read

NPM MCP Banner

NPM MCP

Model Context Protocol server for npm registry

Search packages, check security, compare versions, and validate compatibility. Use it from Cursor AI or Claude Desktop.

Note: This is an unofficial, community-driven MCP server and is not affiliated with or endorsed by npm, Inc.

Features

  • Auto-Security — AI automatically checks packages before suggesting install (no user action!)
  • Capabilities Analysis — ESM/CJS, TypeScript, Platform support (Node/Browser/Deno), Build tools
  • Quick Start Generator — Ready-to-use code examples for any package
  • Package Comparison — Compare alternatives side-by-side (features, size, popularity)
  • Bundle Size Analysis — Minified/gzipped sizes, tree-shaking, impact on your bundle
  • Similar Packages — Find alternatives and similar packages
  • Search — Find packages with ranking and scores
  • Details — Versions, dependencies, download stats, deprecation status
  • Security — Vulnerability check and safe version tips
  • Compatibility — Peer dependency and version conflicts
  • Quality — Maintenance and community metrics
  • Version compare — Breaking changes and semver
  • NPX check — Validate npx commands before running

Install & use

No global install. Add to Cursor or Claude config:

Cursor — ~/.cursor/mcp.json:

json
{
  "mcpServers": {
    "npm-registry-mcp": {
      "command": "npx",
      "args": ["@alisaitteke/npm-mcp"]
    }
  }
}

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json
{
  "mcpServers": {
    "npm-registry-mcp": {
      "command": "npx",
      "args": ["@alisaitteke/npm-mcp"]
    }
  }
}

Global install (optional)

bash
npm install -g @alisaitteke/npm-mcp

Then use "command": "npm-mcp" (no args) in the config above.

What you can ask

Once the server is connected, you can ask things like:

  • “Search for React state management libraries”
  • “Security audit for express@4.18”
  • “Is lodash@4.17 compatible with my current deps?”
  • “Compare React 17 and 18”
  • “Quality check for date-fns”
  • “Is it safe to run npx create-next-app?”

License

MIT

Contributors

Ali Sait Teke
Ali Sait Teke

Creator & Maintainer

Thanks to everyone who helps improve this project!

Contributors

Similar modules

Browse Vulnerability management