Skip to main content
Glama

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

Related MCP server: NPM Sentinel MCP

Install & use

No global install. Add to Cursor or Claude config:

Cursor — ~/.cursor/mcp.json:

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

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

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

Global install (optional)

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

Thanks to everyone who helps improve this project!

Contributors

Available Tools

12 tools
analyze_bundle_sizeA

Analyze bundle size impact and answer "how big is this package?" or "will this slow down my app?" questions. Returns minified size, gzipped size, tree-shaking support analysis, and generates recommendations for lighter alternatives if package is large. Includes comparison with similar packages and actionable advice.

Inputs: packageName (required), version.

analyze_capabilitiesA

Analyze package technical capabilities to answer "does this support ESM/TypeScript?" or "what platforms does this work on?" questions. Shows module system (ESM/CJS), TypeScript support, platform compatibility (Node/Browser/Deno), build tools, and engine requirements.

Inputs: packageName (required), version.

analyze_npx_commandB

Analyze and validate an npx command before execution (security check)

Inputs: command (required), args, timeout.

analyze_qualityC

Evaluate package quality metrics including maintenance, popularity, and sustainability

Inputs: packageName (required).

audit_securityB

Check package for known security vulnerabilities and get recommendations

Inputs: packageName (required), version.

check_compatibilityB

Analyze compatibility of a package with existing project dependencies

Inputs: packageName (required), existingDependencies (required), version.

compare_packagesA

Compare multiple npm packages side-by-side to answer "which is better?" or "what are the pros/cons?" questions. IMPORTANT: This tool generates detailed comparison analysis including: module system (ESM/CJS), TypeScript support, popularity metrics, maintenance status, bundle sizes, and provides a scored recommendation with reasoning. Output is a comprehensive comparison report with pros/cons for each package and a winner recommendation.

Inputs: packages (required).

compare_versionsB

Compare different versions of a package and analyze breaking changes

Inputs: toVersion (required), fromVersion (required), packageName (required).

find_similar_packagesA

Find alternative or similar packages based on keywords and functionality. Use this when users ask "what else is like X?" or "alternatives to Y?" or "other options besides Z?". Returns ranked list of similar packages with scores, descriptions, and download stats. Helps discover packages user might not know about.

Inputs: packageName (required), limit.

generate_quick_startA

Generate ready-to-use code examples and installation instructions. Use this when users ask "how do I use X?" or "show me example code for Y" or want to quickly start using a package. Provides install commands, basic usage, and framework-specific examples.

Inputs: packageName (required), version, framework.

get_package_detailsA

Get detailed information about a specific npm package including versions, dependencies, and repository info

Inputs: packageName (required), version.

search_packagesA

Search and discover npm packages. Use this to find libraries, compare options, see what's available for a specific task, or answer "what packages exist for X?" questions. Returns packages with popularity ranking, descriptions, download stats, and quality scores. Output includes package names, versions, descriptions, and can be used as input for compare_packages.

Inputs: query (required), limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of npm package interaction: searching, comparing, analyzing security, quality, capabilities, bundle size, and generating code. Though some tools are related, their descriptions clearly differentiate purposes (e.g., search_packages finds packages by keyword, find_similar_packages finds alternatives to a given package). No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_packages, analyze_quality, get_package_details). The verbs are descriptive and each noun is appropriate for the operation. This is a uniform, predictable naming convention.

    Tool Count5/5

    With 12 tools, the server is well-scoped for its purpose of npm package analysis and discovery. Each tool covers a distinct need without bloat, fitting comfortably within the ideal 3-15 range. The count supports thorough functionality without overwhelming an agent.

    Completeness5/5

    The tool set covers the full spectrum of package evaluation: discovery, detailed inspection, version comparison, security audits, quality analysis, compatibility checking, bundle size analysis, and quick-start code generation. There are no obvious dead ends—after finding a package, an agent can analyze it in multiple ways and even get usage examples. The surface is complete for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that allows AI models to fetch detailed information about npm packages and discover popular packages in the npm ecosystem.
      1
      1
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI-powered analysis of NPM packages through multiple tools for security vulnerability scanning, dependency analysis, package comparison, and quality assessment.
      19
      361 npm
      19
      TypeScript
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables language models to interact with npm services securely, providing tools for package management, project initialization, script execution, and security auditing.
      MIT