mcp-server-npm-plus
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 |
|---|---|
| searchC | Search npm packages by query. Returns name, version, description, and keywords. |
| package_infoB | Get detailed info about an npm package: description, license, repo, dependencies. |
| downloadsC | Get download statistics for an npm package. |
| compare_downloadsC | Compare download counts across multiple packages. |
| bundle_sizeB | Get bundle size (minified + gzip) for an npm package via Bundlephobia. |
| vulnerabilitiesB | Get vulnerability info for an npm package. Note: Full audit requires npm audit in project context. |
| dependency_treeC | Get dependency tree for an npm package (direct deps only). |
| download_trendsB | Get download trends (daily breakdown + sparkline) for an npm package. |
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 8 tools
Each tool has a clearly distinct purpose targeting specific aspects of npm package analysis, such as bundle size, downloads, dependencies, vulnerabilities, and search. There is no overlap in functionality, making it easy for an agent to select the right tool for each task.
Most tools follow a consistent snake_case naming pattern with clear verbs and nouns, like 'bundle_size', 'downloads', and 'package_info'. However, 'dependency_tree' uses a compound noun without a verb, which is a minor deviation from the otherwise uniform style.
With 8 tools, the server is well-scoped for npm package analysis, covering key areas like size, downloads, dependencies, info, search, and vulnerabilities. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for npm package analysis, including info retrieval, dependency inspection, download trends, and vulnerability checks. A minor gap exists in direct package management actions like install or update, but core analysis workflows are fully supported.