NPM Context Agent 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_readme_dataB | Get README file content from a package's GitHub repository |
| search_packagesC | Search npm registry for packages by keyword |
| get_package_versionsB | Get all available versions of a package |
| get_package_dependenciesB | Get dependencies, devDependencies, and peerDependencies for a package |
| get_download_statsB | Get download statistics from npm |
| get_package_infoC | Get comprehensive package metadata |
| compare_packagesC | Compare two packages side-by-side |
| get_package_sizeC | Get bundle size information from bundlephobia |
| get_package_qualityB | Get quality metrics from npms.io |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-package | Comprehensive analysis of an npm package |
| compare-packages | Compare two npm packages |
| find-alternatives | Find alternative packages |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose targeting specific aspects of npm package analysis, with no ambiguity or overlap. For example, get_package_info provides general metadata while get_package_quality focuses on npms.io metrics, and get_package_size handles bundlephobia data.
All tools follow a consistent verb_noun pattern with snake_case throughout, using descriptive action verbs like 'get', 'search', and 'compare' paired with specific nouns. This creates a predictable and readable naming convention across all nine tools.
Nine tools is well-scoped for npm package analysis, providing comprehensive coverage without bloat. Each tool earns its place by addressing distinct aspects like metadata, dependencies, versions, quality metrics, and search functionality.
The tool set provides excellent coverage for npm package research and comparison, including search, metadata, dependencies, versions, quality metrics, and bundle analysis. Minor gaps might include package installation/management operations or deeper GitHub integration beyond README access, but core workflows are well-supported.