Este es un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona funcionalidad para obtener información sobre los paquetes npm.
Búsqueda de paquetes : herramienta para obtener información detallada sobre los paquetes npm
Paquetes populares : recurso para enumerar los 10 paquetes npm más populares
Related MCP server: NPM Helper MCP
Para instalar NPM MCP Server para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install @mateusribeirocampos/npm-mcp-server --client claudenpm installnpm run buildnpm startPara desarrollo:
npm run devEl servidor expone dos funcionalidades principales:
Obtiene información detallada sobre un paquete npm específico. La herramienta devuelve información completa del paquete, incluyendo:
Nombre del paquete
Última versión
Descripción
Información del autor
URL de la página de inicio
URL del repositorio
Lista de dependencias
Ejemplo de uso:
const result = await server.tools.searchNpmPackage({ packageName: "react" });Ejemplo de respuesta:
{
"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"
}
}Lista los 10 paquetes npm más populares, ordenados por popularidad. Cada paquete de la lista incluye:
Nombre del paquete
Descripción
Versión actual
URI del recurso: npm://popular
Ejemplo de respuesta:
[
{
"name": "lodash",
"description": "Lodash modular utilities",
"version": "4.17.21"
},
// ... more packages
]Este servidor MCP se puede integrar con modelos de IA para:
Obtenga información del paquete antes de la instalación
Comparar diferentes versiones de paquetes
Analizar dependencias
Encuentra alternativas populares
Obtenga resúmenes rápidos de paquetes
Mecanografiado
SDK de protocolo de contexto de modelo
Obtención de nodos
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0searchNpmPackageScored across 1 tool
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.
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…