Skip to main content
Glama
enesjakozh
btwiuse

npm-search-mcp-server

by btwiuse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor MCP npm-search

insignia de herrería

Un servidor de protocolo de contexto de modelo que le permite buscar paquetes npm llamando al comando npm search .

Herramientas disponibles

  • search_npm_packages : busca paquetes npm.

    • Argumentos obligatorios:

      • query (cadena): La consulta de búsqueda.

Captura de pantalla de Claude

Instalación

Instalación mediante herrería

Para instalar npm-search para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install npm-search-mcp-server --client claude

Uso de NPM (recomendado)

Alternativamente, puede instalar npm-search-mcp-server a través de npm:

npm install -g npm-search-mcp-server

Después de la instalación, puedes ejecutarlo como un comando usando:

npm-search-mcp-server

Usando uv

Al usar uv , no se requiere ninguna instalación específica. Usaremos uvx para ejecutar directamente npm-search-mcp-server .

Related MCP server: mcp-server-npm

Configuración

Configurar para Claude.app

Añade a tu configuración de Claude:

"mcpServers": {
  "npm-search": {
    "command": "npx",
    "args": ["-y", "npm-search-mcp-server"]
  }
}
"mcpServers": {
  "npm-search": {
    "command": "uvx",
    "args": ["npm-search-mcp-server"]
  }
}

Configurar para Zed

Añade a tu configuración Zed settings.json:

"context_servers": {
  "npm-search-mcp-server": {
    "command": "npx",
    "args": ["-y", "npm-search-mcp-server"]
  }
},
"context_servers": [
  "npm-search-mcp-server": {
    "command": "uvx",
    "args": ["npm-search-mcp-server"]
  }
],

Ejemplos de interacciones

  1. Buscar paquetes npm:

{
  "name": "search_npm_packages",
  "arguments": {
    "query": "express"
  }
}

Respuesta:

{
  "results": [
    {
      "name": "express",
      "description": "Fast, unopinionated, minimalist web framework",
      "version": "4.17.1",
      "author": "TJ Holowaychuk",
      "license": "MIT"
    },
    ...
  ]
}

Depuración

Puede usar el inspector MCP para depurar el servidor. Para instalaciones uvx:

npx @modelcontextprotocol/inspector npx -y npm-search-mcp-server

O si ha instalado el paquete en un directorio específico o está desarrollando en él:

cd path/to/servers/src/npm-search
npx @modelcontextprotocol/inspector uv run npm-search-mcp-server

Ejemplos de preguntas para Claude

  1. Buscar paquete exprés en npm

  2. "Buscar paquetes relacionados con React"

  3. Muéstrame los paquetes npm para desarrollo web

Construir

Compilación de Docker:

cd src/npm-search
docker build -t mcp/npm-search .

Contribuyendo

Invitamos a todos a contribuir para expandir y mejorar npm-search-mcp-server. Ya sea que desee agregar nuevas herramientas relacionadas con npm, mejorar la funcionalidad existente o mejorar la documentación, su aporte es valioso.

Para ver ejemplos de otros servidores MCP y patrones de implementación, consulte: https://github.com/modelcontextprotocol/servers

¡Aceptamos solicitudes de incorporación de cambios! Siéntete libre de contribuir con nuevas ideas, correcciones de errores o mejoras para que npm-search-mcp-server sea aún más potente y útil.

Licencia

npm-search-mcp-server cuenta con la licencia MIT. Esto significa que puede usar, modificar y distribuir el software libremente, sujeto a los términos y condiciones de la licencia MIT. Para más detalles, consulte el archivo de LICENCIA en el repositorio del proyecto.

Available Tools

1 tool
search_npm_packagesC

Search for npm packages

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Search for npm packages') without detailing traits like rate limits, authentication needs, pagination, or response format. This leaves significant gaps in understanding how the tool behaves in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it lacks front-loaded critical information and could benefit from more structure to enhance clarity, but it avoids unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It fails to address behavioral aspects like search result format, limitations, or error handling, which are essential for an agent to use the tool effectively despite the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'query' parameter documented as 'Search query'. The description does not add any meaning beyond this, such as examples or constraints on the query format. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search for npm packages' clearly states the verb (search) and resource (npm packages), making the basic purpose understandable. However, it lacks specificity about what kind of search this is (e.g., keyword search, advanced filtering) and doesn't differentiate from potential siblings since none exist, though it remains somewhat vague in scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context for its application. With no sibling tools, this is less critical, but it still offers no usage instructions, leaving the agent to infer based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedsearch_npm_packages
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'search_npm_packages' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server named 'npm-search-mcp-server', which suggests a broader npm-related scope. A single search tool feels thin and incomplete for interacting with npm packages beyond basic searches.

Completeness2/5

The tool surface is severely incomplete for npm package management. It only provides search functionality, lacking essential operations like getting package details, checking versions, or managing dependencies, which are core to the domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches