Skip to main content
Glama
enesjakozh
btwiuse

npm-search-mcp-server

by btwiuse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

npm-search MCP 서버

대장간 배지

npm search 명령을 호출하여 npm 패키지를 검색할 수 있는 모델 컨텍스트 프로토콜 서버입니다.

사용 가능한 도구

  • search_npm_packages - npm 패키지를 검색합니다.

    • 필수 인수:

      • query (문자열): 검색 쿼리.

클로드 스크린샷

설치

Smithery를 통해 설치

Smithery 를 통해 Claude Desktop용 npm-search를 자동으로 설치하려면:

지엑스피1

NPM 사용(권장)

또는 npm을 통해 npm-search-mcp-server 설치할 수 있습니다.

npm install -g npm-search-mcp-server

설치 후 다음을 사용하여 명령으로 실행할 수 있습니다.

npm-search-mcp-server

uv를 사용하여

uv 사용하면 별도의 설치가 필요하지 않습니다. uvx 사용하여 npm-search-mcp-server를 직접 실행합니다.

Related MCP server: mcp-server-npm

구성

Claude.app에 대한 구성

Claude 설정에 추가:

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

Zed에 대한 구성

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"]
  }
],

예시 상호작용

  1. npm 패키지 검색:

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

응답:

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

디버깅

MCP 검사기를 사용하여 서버를 디버깅할 수 있습니다. UVX 설치의 경우:

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

또는 특정 디렉토리에 패키지를 설치했거나 해당 디렉토리에서 개발 중인 경우:

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

클로드에 대한 질문의 예

  1. "npm에서 express 패키지를 검색하세요"

  2. "React 관련 패키지 찾기"

  3. "웹 개발을 위한 npm 패키지를 보여주세요"

짓다

Docker 빌드:

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

기여하다

npm-search-mcp-server의 확장 및 개선을 위한 기여를 환영합니다. 새로운 npm 관련 도구를 추가하거나, 기존 기능을 강화하거나, 문서를 개선하는 등 어떤 목적이든 여러분의 의견은 소중합니다.

다른 MCP 서버 및 구현 패턴의 예는 https://github.com/modelcontextprotocol/servers를 참조하세요.

풀 리퀘스트를 환영합니다! npm-search-mcp-server를 더욱 강력하고 유용하게 만들기 위한 새로운 아이디어, 버그 수정, 개선 사항을 자유롭게 공유해 주세요.

특허

npm-search-mcp-server는 MIT 라이선스에 따라 라이선스가 부여됩니다. 즉, MIT 라이선스의 조건에 따라 소프트웨어를 자유롭게 사용, 수정 및 배포할 수 있습니다. 자세한 내용은 프로젝트 저장소의 LICENSE 파일을 참조하세요.

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