The NPM MCP Server provides tools to fetch and analyze npm package information:
Search npm packages: Fetch detailed information about specific packages (name, version, description, author, homepage, repository, dependencies)
List popular packages: Retrieve the 10 most popular npm packages with their names, descriptions, and versions
Integrate with AI workflows: Support for package comparison, dependency analysis, and finding alternatives
Development modes: Supports both production (npm start) and development (npm run dev) environments
Allows retrieval of Lodash package information as part of the popular packages resource functionality.
Provides tools for searching and retrieving detailed information about npm packages, including package metadata, version information, dependencies, and popularity rankings.
Enables access to React package information including version details, description, and repository data to support development decisions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@NPM MCP Server show me details about the express package"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This is a Model Context Protocol (MCP) server that provides functionality to fetch information about npm packages.
Package Search: Tool to fetch detailed information about npm packages
Popular Packages: Resource to list the 10 most popular npm packages
Related MCP server: NPM Helper MCP
To install NPM MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @mateusribeirocampos/npm-mcp-server --client claudenpm installnpm run buildnpm startFor development:
npm run devThe server exposes two main functionalities:
Fetches detailed information about a specific npm package. The tool returns comprehensive package information including:
Package name
Latest version
Description
Author information
Homepage URL
Repository URL
Dependencies list
Example usage:
const result = await server.tools.searchNpmPackage({ packageName: "react" });Example response:
{
"name": "react",
"version": "18.2.0",
"description": "React is a JavaScript library for building user interfaces.",
"author": "Meta Open Source",
"homepage": "https://reactjs.org/",
"repository": {
"url": "https://github.com/facebook/react.git"
},
"dependencies": {
"loose-envify": "^1.1.0"
}
}Lists the 10 most popular npm packages, sorted by popularity. Each package in the list includes:
Package name
Description
Current version
Resource URI: npm://popular
Example response:
[
{
"name": "lodash",
"description": "Lodash modular utilities",
"version": "4.17.21"
},
// ... more packages
]This MCP server can be integrated with AI models to:
Get package information before installation
Compare different package versions
Analyze dependencies
Find popular alternatives
Get quick package summaries
TypeScript
Model Context Protocol SDK
Node-fetch
Zod
| Name | Required | Description | Default |
|---|---|---|---|
| packageName | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'searchNpmPackage' has a distinct and clear purpose by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'searchNpmPackage' uses a consistent verb_noun pattern with no deviations to evaluate.
A single tool is too few for a server named 'NPM MCP Server', which implies broader npm-related functionality. This feels thin and incomplete for the apparent scope of npm package management.
The tool set is severely incomplete for an npm server. Only search functionality is provided, with no coverage for install, view, publish, update, or other essential npm operations, leading to significant gaps.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mateusribeirocampos/npm-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server