npm-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_packagesA | Search the npm registry for packages matching a query. Returns name, description, version, score, and links. Use this to find packages for a specific task or compare options. |
| get_packageA | Get detailed information about a specific npm package including latest version, dependencies, download stats, size, and repository links. |
| compare_packagesA | Compare multiple npm packages side by side. Shows downloads, size, dependencies, and quality scores to help choose between alternatives. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a clear, distinct purpose: searching for packages, fetching details of a specific package, and comparing alternatives. No overlap in functionality.
All tool names follow a consistent verb_noun pattern: search_packages, get_package, compare_packages. The pattern is uniform and predictable.
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.
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.