npm is the world's largest software registry, used by JavaScript developers to share and borrow packages for their projects.
Why this server?
Available as an npm package for easy installation and execution, with support for providing API credentials through command line arguments.
Why this server?
Supports package installation and updates for the MCP server through npm's package management system.
Why this server?
Used for package installation and management of the MCP server.
Why this server?
Uses npm (v6 or higher) for package management and dependency installation.
Why this server?
Provides tools for querying package information, versions, and vulnerabilities from npm registry through JFrog's package service integration.
Why this server?
Available as an npm package (@302ai/browser-use-mcp) for easy installation and usage with browser automation capabilities
Why this server?
Supports distribution and installation via the npm registry for easy deployment.
Why this server?
Enables installation and distribution of the MCP server through the npm package registry.
Why this server?
Allows the MCP server to be installed and run via NPX, making it easy to integrate Vapi's capabilities through the NPM package ecosystem.
Why this server?
Enables running the Chargebee MCP server through npm's npx command, providing access to Chargebee's documentation and code generation capabilities.
Why this server?
Allows easy installation and deployment of the Token Metrics MCP server through npm, providing cryptocurrency analysis tools and market data access
Why this server?
Uses npm for package management and installation of the MCP server.
Why this server?
Supports installation and package management through npm.
Why this server?
Uses npm ecosystem for package distribution and installation via npx
Why this server?
Available as an npm package (@debugg-ai/debugg-ai-mcp) for easy installation and integration
Why this server?
Provides a way to install and run the Infisical MCP server using npx commands from the npm registry.
Why this server?
Supports installation and building of the MCP server through npm package management, with commands for dependencies, building, and running the inspector.
Why this server?
Enables installation and execution of the CoinStats MCP server via NPX, making it easy to run the server without manual installation steps.
Why this server?
Distributes the MCP server through npm packages for easy installation and updates
Why this server?
Offers installation of the Novita MCP server package through npm package manager.
Why this server?
Used for package building and installation during setup, but not a primary integration target of the MCP server's functionality.
Why this server?
Enables installation and distribution of the MCP server through the npm registry, supporting both global installation and direct execution with npx.
Why this server?
Enables package discovery and analysis in the Node.js ecosystem, with capabilities to research metadata, dependencies, and repository connections
Why this server?
Used for package management and running scripts for development, testing, and linting.
Why this server?
Provides package distribution through npm, with version tracking and dependency management
Why this server?
The AutoMobile tool is published on npm, allowing users to install and use the mobile automation toolset.
Why this server?
Used for package management and running scripts.
Why this server?
Enables installation and execution of the task manager via NPM packages, with support for registering and managing complex multi-step tasks.
Why this server?
Allows installation and execution of the MCP server using npm packages, with download statistics tracked through NPM.
Why this server?
Publishes to npm registry allowing installation via npm, with version tracking displayed through npm badge.
Why this server?
Allows installation and execution of the Moralis MCP server via NPM, making it accessible through the command 'npx @moralisweb3/api-mcp-server'.
Why this server?
Used as a package manager for installing and managing dependencies of the MCP server.
Why this server?
Available as an npm package for easy installation and updates
Why this server?
Provides an npm package for enabling Glean's enterprise search and AI assistant capabilities in supported MCP clients.
Why this server?
Integration for package deployment and publishing through NPM's registry
Why this server?
Provides package management for the Letta MCP server, managing dependencies and offering scripts for building and running the server.
Why this server?
Required package manager, version 8 or higher needed for dependency management.
Why this server?
Distributed through npm registry, allowing installation and execution via npx or global installation
Why this server?
Allows installing and running the Raindrop.io MCP server via npx command
Why this server?
Supports distribution via npm, allowing easy installation and versioning of the MCP server.
Why this server?
Shows the package version from npm registry and provides installation capabilities using npx.
Why this server?
Used for installation, building, and running the fountain pen ink MCP server and its dependencies.
Why this server?
Available as an npm package for easy installation and dependency management.
Why this server?
Enables installation and execution of the MCP server through npx, allowing users to run the Heim MCP server without installing it permanently.
Why this server?
Allows installation and distribution of the AI Note MCP server package through npm registry, making it easily accessible for Claude Desktop users.
Why this server?
Handles package installation, dependency management, and publishing for the MCP server.
Why this server?
Distributes the server via npm package management system, allowing for easy installation.
Why this server?
Enables installation and execution of the MCP server through npm package management
Why this server?
Provides installation methods via npm, including using npx to run the server directly or installing the package globally.
Why this server?
Used for server installation and dependency management with npm commands for setup and execution.
Why this server?
Used for managing Node.js dependencies and running the MCP server
Why this server?
Uses npm for dependency management and running build/test commands
Why this server?
Distributes the Dart MCP server as an npm package, enabling easy installation and updates through the npm registry.
Why this server?
Enables installation and execution of the MCP server using NPX, allowing for easy deployment without manual installation.
Why this server?
Supports installation and management of dependencies through npm, with commands for building and running the server.
Why this server?
Packaged as an npm module (@terrakube/mcp-server-terrakube) that can be installed and executed with npx.
Why this server?
Used for installation and package management of the MCP server components.
Why this server?
Distributes the MCP server as an npm package, as indicated by the npm version badge.
Why this server?
Distributed as an npm package (@geocoding-ai/mcp) that can be installed and run via npx
Why this server?
Supports installation and management of the MCP server dependencies through npm commands for building, testing, and running the server.
Why this server?
Provides package availability information and installation capabilities through the NPM registry.
Why this server?
Provides access to the ReviewWebsite.com API, allowing AI assistants to create and manage website reviews, extract data from URLs, convert URLs to markdown, scrape content, extract links, and summarize websites.
Why this server?
Supports installation and execution through npm, enabling easy deployment of the MCP server globally or via npx.
Why this server?
Provides package management functionality for installing dependencies and building the MCP server project
Why this server?
The MCP server is distributed as an npm package that can be installed and run using npx.
Why this server?
Available as an npm package for easy installation and integration into Node.js projects.
Why this server?
Provides distribution as an NPM package for easy installation.
Why this server?
Used to install and run the HubSpot MCP server through the npx command.
Why this server?
Used for package management and running scripts within the project.
Why this server?
Provides packaging and distribution through npm, with commands for version management and publishing
Why this server?
Provides accessibility audit tools that can be installed and run via npm, allowing for detailed a11y testing of webpages with configurable WCAG criteria
Why this server?
Provides package management for installing dependencies and running the server through npm commands.
Why this server?
Enables installation and execution through npm packages, supporting both direct installation and execution via npx.
Why this server?
Allows access to npm package documentation through the ref_search_documentation tool, enabling AI agents to look up and retrieve information about npm packages, their APIs, and usage.
Why this server?
Distributes the MCP server as an npm package, making it easy to install and update through the npm package registry.
Why this server?
Monitors the operational status of npm registry and related services, reporting on current availability and performance.
Why this server?
Uses npm for package management and running scripts to build, test, and deploy the Azure DevOps MCP server.
Why this server?
Available as an npm package (deebo-setup) for easy installation and configuration
Why this server?
The MCP server uses npm for package management and running development commands
Why this server?
ATLAS can be installed via npm package management system and provides npm scripts for database backup and restore operations.
Why this server?
Available as an npm package for installation and distribution.
Why this server?
Distributed as an npm package with version tracking and badge integration for easy installation and updates.
Why this server?
Enables installation and execution of the code reasoning MCP server through the npm package registry, with support for both global installation and direct execution via npx.
Why this server?
Allows installation and distribution of the MCP server package via npm, with the package published as @bujaayjaay/mcp-coincap-jj.
Why this server?
Allows installation and execution of the MCP server through npm, either globally or via npx.
Why this server?
Provides installation and distribution of the nlobby-mcp package to enable easy setup of the MCP server
Why this server?
Provides the package management and distribution mechanism for installing the MCP server.
Why this server?
Enables running the MCP server directly through NPX, allowing users to execute the package without installing it locally.
Why this server?
Offers package distribution through NPM for easy installation and dependency management
Why this server?
Enables installation and execution via npm's package manager, supporting both local installation and execution via npx without installation.
Why this server?
Available as an npm package that can be installed globally to enable screenshot functionality.
Why this server?
Enables installation, building, and running the MCP server through npm commands, with support for dependency management.
Why this server?
Facilitates package management and publishing of the MCP server to the NPM registry.
Why this server?
Enables installing and managing npm packages for React projects
Why this server?
Integrates with remote npm registry for real-time security vulnerability scanning of npm packages
Why this server?
Provides documentation lookups for NPM packages via registry documentation, supporting both public and private registries with automatic configuration detection from .npmrc
Why this server?
Distributed as an npm package for easy installation and integration, with both global CLI usage and programmatic API access.
Why this server?
Enables easy installation and execution via npx command, with the package published to the npm registry for simplified deployment.
Why this server?
Provides tools for analyzing npm dependencies, checking for outdated packages, and offering detailed update recommendations with version information.
Why this server?
Uses npm for package management, dependency installation, and running server commands.
Why this server?
Provides installation and dependency management through npm, allowing users to easily set up and run the MCP server.
Why this server?
Supported as an alternative package manager for installing and managing the Buttondown API integration package.
Why this server?
The server requires npm as a prerequisite and uses npm commands for building and linking
Why this server?
Supports debugging via the MCP Inspector which can be launched using npm to monitor and troubleshoot the MCP server communications.
Why this server?
Provides package installation and management for the COS MCP server, supporting global and local installation options.
Why this server?
Enables installation of the MCP server via npm, providing access to NPM package management for installing and running the file context server.
Why this server?
Supports installation and deployment via NPM package registry as '@tmhr1850/backlog-mcp-server'
Why this server?
Manages package dependencies and enables installation through NPM
Why this server?
Allows installation and execution of the MCP server through npm, supporting both global and local installation patterns.
Why this server?
Used as the package manager for installing and running the MCP server package.
Why this server?
Package manager used for installing dependencies and running the MCP server through commands like 'npx'.
Why this server?
Used as one of the package managers for installing dependencies and running scripts.
Why this server?
Used for building and running the MCP server that bridges between AI agents and Adobe Premiere Pro
Why this server?
Package distribution platform where the MCP server is published and can be installed from
Why this server?
Used for dependency management of the MCP server, which enables remote control and querying of Adobe Premiere Pro projects
Why this server?
Enables installation and distribution of the MCP server package through npm.
Why this server?
Allows installation and distribution of the Neo N3 MCP server as a package through the NPM registry, making it easily accessible to users.
Why this server?
Supports distribution and installation via npm packages, with automated release versioning and NPM distribution capabilities.
Why this server?
The MCP server can be installed and run via npm, the Node.js package manager, using the package @dasheck0/face-generator.
Why this server?
Detects and uses npm package manager for component installation and updates through the get_package_manager tool
Why this server?
Enables connecting to other MCP servers through npm packages using npx commands
Why this server?
Integrates with npm for running project commands including tests, linting, and builds through standardized tools.
Why this server?
Enables installation of the package through npm package manager, supporting both global installation and dependency management.
Why this server?
Used for package management and running the server, with commands for installation, building, and starting the MCP server.
Why this server?
Available as an npm package for easy installation and integration with MCP clients.
Why this server?
Used for package management and running scripts to build, start, and develop the MCP server.
Why this server?
Used for installing dependencies required by the wallet generator MCP server.
Why this server?
Uses npm for package management and running scripts (build, start) for the server.
Why this server?
Allows installation and execution of the MCP server package through the npm registry.
Why this server?
Enables installation and execution of the Sensei MCP server through the npm package manager using npx commands.
Why this server?
Provides installation and distribution of the MCP server through npm packages, allowing users to install via npx or global CLI commands
Why this server?
Offers comprehensive NPM package analysis including version tracking, dependency mapping, security scanning, and quality metrics
Why this server?
Enables distribution and installation of the MCP server as an npm package, with tracking of downloads and usage
Why this server?
Used for installation and setup of the AlphaFold MCP server components
Why this server?
Used for installation and building the MCP server.
Why this server?
Used for package management and running server operations like installation, building, and starting the PubChem MCP server.
Why this server?
Supports package management for server installation and dependency handling, making it easy to set up and maintain the PubChem MCP server environment.
Why this server?
Used for managing dependencies and building the server
Why this server?
Used for installation and package management of the Gene Ontology MCP server.
Why this server?
Uses npm for package management, installation, and running server commands
Why this server?
Used for managing dependencies and building the project, required for installation (v7 or higher)
Why this server?
Provides installation through npm package registry, supporting both global and local installation options
Why this server?
Enables installation of the penetration testing toolkit via npm package management
Why this server?
Enables publishing and distribution of customized MCP server packages through npm, with automatic versioning based on Git tags.
Why this server?
Enables deployment as an npm package that can be installed and executed using npm commands
Why this server?
Provides package distribution through npm registry, enabling installation via npm commands and integration with package.json workflows.
Why this server?
Utilizes the mcp-remote package from npm for secure connections
Why this server?
Provides package management for installing the Opentrons MCP server via the recommended installation method.
Why this server?
Supports distribution and installation through the npm package registry, allowing users to easily install and run the server using npm commands.
Why this server?
Distributes the Emlog MCP server as an npm package for easy installation and updates
Why this server?
Offers package distribution through the npm registry, enabling installation via npm commands
Why this server?
Distributed through npm package registry as '@grec0/mcp-s2s-asterisk', enabling easy installation and updates.
Why this server?
Package manager used to install dependencies and run the MCP server.
Why this server?
Provides installation of the MCP server dependencies through Node.js package management
Why this server?
Allows running npm package management commands through the Shell MCP server for JavaScript/TypeScript project management.
Why this server?
Provides installation and deployment through npm, allowing users to easily set up the MCP server using 'npx -y apisix-mcp' with configurable environment variables.
Why this server?
Enables distribution and installation of the MCP server as an NPM package with the @blueperfumery/mcp-server package name.
Why this server?
Available through npm package registry for installation.
Why this server?
Allows installation and execution of the MCP server through npm packages, with version tracking and dependencies managed through the npm registry.
Why this server?
Offers integration through a published npm package for easy installation and configuration of the Memory Bank MCP
Why this server?
Provides installation method for the SMCP server package via npm package registry
Why this server?
Used for package management and running the server, with commands for installation, building, and executing the QuickBase MCP server.
Why this server?
Used for package management and running scripts to build and start the server.
Why this server?
Provides installation of the Pokemon Paste MCP server through the npm registry for easy deployment.
Why this server?
Available as an npm package for easy installation and integration into existing projects.
Why this server?
Used for package management and distribution of the Pokémon VGC Damage Calculator MCP server
Why this server?
Used for package management and running scripts within the MCP server project.
Why this server?
Used for package installation, dependency management, and running scripts for the server.
Why this server?
Available as an npm package for easy installation and integration into existing projects.
Why this server?
Used for package management and running build/start commands
Why this server?
Used for installing dependencies and building the project
Why this server?
Used for package management and running scripts for the MCP server installation and operation.
Why this server?
Provides dependency tracking and task management for projects using npm package management.
Why this server?
Enables installation and management through npm, with support for npm link to make the command globally available.
Why this server?
Integrates with npm for package installation and management of the Exa MCP server
Why this server?
Allows installation and usage of the 12306-mcp package via npm to provide train ticket search functionality to AI models
Why this server?
Supports the installation and dependency management through package.json, allowing the MCP server to be installed and run for cybersecurity API testing purposes.
Why this server?
Used to install and run the Actor-Critic Thinking MCP server through NPX, enabling dual-perspective analysis for creative content evaluation.
Why this server?
Allows searching for Yeoman templates on npm registry
Why this server?
Used for package management and running the MCP server, both locally and via npx for the latest version.
Why this server?
Supports using npm as a package manager when installing shadcn/ui components and blocks
Why this server?
Available as an npm package for easy installation and integration with Onyx knowledge bases
Why this server?
Package manager used for installing dependencies and running the server, with version 7+ required.
Why this server?
Supports running npm commands like 'npm run build' for JavaScript project management
Why this server?
Handles package management and dependency installation for the TaskFlow MCP server
Why this server?
Used for package management and running scripts for the MCP server
Why this server?
Used for package installation and management of the Lulu Print MCP server
Why this server?
Supports package installation and management through npm.
Why this server?
Allows searching for npm packages by executing the npm search command, enabling users to find and explore available packages in the npm registry with their name, description, version, author, and license information.
Why this server?
Provides a package (proofly-mcp) that acts as an MCP server for deepfake detection, installable via npm either globally or locally.
Why this server?
Provides tools for checking latest stable package versions from the npm registry for Node.js/JavaScript packages
Why this server?
Used for package distribution and installation, with commands for starting the server in standard and development modes
Why this server?
Used for installing dependencies and running build commands for the server.
Why this server?
Supported as a package manager for installing and managing dependencies.
Why this server?
Supports publishing the MCP server as an npm package, allowing for easy distribution and installation in Claude Desktop environments.
Why this server?
Distributes the MCP server through npm, enabling easy installation and execution of the DynamoDB connection service.
Why this server?
Enables package management through Angular CLI commands like 'ng add' to add packages and 'ng update' to update Angular packages and dependencies in the workspace.
Why this server?
Package manager used for installing dependencies, with version 9 or higher required.
Why this server?
Used for installation and package management of the MCP server.
Why this server?
Used for installing dependencies and managing the build process for the MCP server.