mcp-npm-tools
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| npm_searchA | Search the npm registry for packages by keyword. Returns name, description, version, weekly downloads, and last publish date for each result. |
| npm_package_infoA | Get detailed information about an npm package: all versions, dependencies, maintainers, repository, license, size, npm score, and weekly downloads. |
| npm_dependency_auditA | Analyze a package.json to find outdated dependencies (compare installed vs latest), deprecated packages, and known security vulnerabilities. |
| npm_bundle_sizeA | Estimate the bundle size of an npm package using the Bundlephobia API. Returns minified size, gzipped size, and dependency count. |
| npm_compare_packagesA | Compare 2 or more npm packages side by side: weekly downloads, bundle size, dependency count, last update, GitHub stars, and license. |
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 5 tools
Each tool targets a distinct aspect of npm packages: searching, detailed info, dependency audit, bundle size, and comparison. No two tools overlap in purpose, and the descriptions make their boundaries clear.
All tool names share the npm_ prefix and use lowercase with underscores, but the pattern mixes verb-first names (npm_search, npm_compare_packages) with noun-phrase names (npm_package_info, npm_dependency_audit). This is generally predictable but not perfectly uniform.
With exactly 5 tools, the server is well-scoped for an npm utility toolkit. Each tool covers a meaningful function without bloat, and the count feels appropriate for the domain.
The set covers the core needs for npm package exploration: search, detailed inspection, dependency auditing, bundle size estimation, and side-by-side comparison. No obvious missing operations within the apparent purpose.