npm-search-mcp
by zcag
README.md
# npm-search-mcp
MCP server that searches npm packages and returns live registry data. No API key needed.
## Tools
- **search_packages** — Search npm for packages by keyword. Returns names, descriptions, download counts, and links.
- **get_package** — Get detailed info about a specific package: version, dependencies, size, weekly downloads.
- **compare_packages** — Compare 2-10 packages side by side with download stats, size, and quality scores.
## Why?
AI coding assistants have stale knowledge about npm packages. This MCP server gives them live access to the npm registry — current versions, download trends, and package details updated in real-time.
## Install
### npx (easiest)
```bash
npx -y github:zcag/npm-search-mcp
```
### Claude Code config
```json
{
"mcpServers": {
"npm-search": {
"command": "npx",
"args": ["-y", "github:zcag/npm-search-mcp"]
}
}
}
```
### Docker
```bash
docker run -i ghcr.io/zcag/npm-search-mcp:1.0.0
```
### From source
```bash
git clone https://github.com/zcag/npm-search-mcp.git
cd npm-search-mcp
npm install && npm run build
node dist/index.js
```
## License
MIT
TDQS
A3.9/5.0
Scored across 3 tools
Disambiguation5/5
Each tool serves a clear, distinct purpose: searching for packages, fetching details of a specific package, and comparing alternatives. No overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: search_packages, get_package, compare_packages. The pattern is uniform and predictable.
Tool Count4/5
With only 3 tools, the server is well-scoped for its purpose. Each tool is essential and non-redundant, though the count is on the lower end of the ideal range.
Completeness4/5
The tool set covers the core workflow of discovering and evaluating npm packages. Minor gaps include lack of package version history or no ability to get all versions, but the primary workflow is complete.
Maintenance
ActivityInactive
ResponsivenessNo issues