NPM

You have a complete MCP server that lets language models interact with npm and its services in a safe, structured way. It provides a set of actions to search, inspect, install, update, audit, and run npm-related tasks, making it easier to reason about npm activities within an automated workspace.

How to use

To use this server with an MCP client, connect your client to the local MCP endpoint described in the installation guide. You can request operations such as searching for packages, getting package details, installing or removing packages, listing installed packages, auditing security, and running scripts defined in your project. Each operation is exposed as a distinct tool you invoke through a standardized command wrapper, returning structured results you can reason about programmatically.

How to install

# Prerequisites
node 18+
npm 9+

# Step 1: Clone the project repository
git clone <este-repositorio>
cd npm-mcp-server

# Step 2: Install dependencies
npm install

# Step 3: Build the TypeScript sources
npm run build

# Step 4: Start the MCP server
npm start

Configuration and usage notes

This MCP server is designed to be used as a standalone service or integrated into an MCP client configuration. The standard integration snippet shows how to register the local server with a client, exposing the npm MCP server via a local Node process.

{
  "mcpServers": {
    "npm": {
      "command": "node",
      "args": ["/ruta/a/npm-mcp-server/main.js"],
      "env": {}
    }
  }
}

Security and reliability notes

All operations are designed to be safe and predictable, with a 30-second timeout on every command, input validation using a schema-based approach, secure error handling, and safeguards to limit operations to specific directories.

Examples of use

You can perform common npm actions by invoking corresponding tools through your MCP client. Examples include searching for packages, installing dependencies, and running project scripts.

Troubleshooting

If you encounter a module not found error, ensure dependencies are installed and run npm install in your project directory. For permission issues with global installations, consider proper permission handling instead of forcing global installs. Commands have a 30-second timeout; for large projects, work within a specific directory.

Notes

The server is intended to be used with npm and optional tooling like npx in examples. Ensure you provide correct paths to the main script when configuring MCP clients.

Available tools

npm_search

Search for packages in the npm registry and return matching results.

npm_info

Retrieve detailed information about a specific npm package, including versions and metadata.

npm_install

Install packages for a project, with options for development and global scope.

npm_uninstall

Remove installed packages from the project.

npm_list

List currently installed packages in the project directory.

npm_outdated

Show packages with newer versions available.

npm_update

Update packages to the latest compatible versions.

npm_run_script

Execute a script defined in package.json by name.

npm_init

Initialize a new npm project in a directory.

npm_audit

Audit the project for known security vulnerabilities.

npm_audit_fix

Automatically apply fixes to known vulnerabilities when possible.