npmlens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for higher API rate limits when fetching GitHub info |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_npmB | Search the npm registry for packages. |
| get_readmeA | Fetch README text for a given npm package (optionally a specific version). |
| get_package_infoA | Get enriched package info: registry metadata, last-week downloads, and GitHub repo details when available. |
| get_downloadsB | Get npm downloads for the last day/week/month. |
| get_usage_snippetB | Extract a likely usage snippet from a package's README. |
| get_package_versionsA | List all available versions of a package with publish dates and dist tags. |
| get_package_dependenciesC | Get the dependency tree for a package. |
| compare_packagesA | Compare multiple npm packages side-by-side (downloads, stars, license, etc.). |
| search_by_keywordsB | Search npm packages by specific keywords/tags. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search-packages | Search for npm packages with examples |
| analyze-package | Get detailed information about a package including README, downloads, and GitHub stats |
| compare-alternatives | Compare multiple packages side-by-side |
| check-dependencies | View a package's dependencies and their versions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| npm Search API | Queries https://registry.npmjs.org/-/v1/search |
| npm Package API | Reads https://registry.npmjs.org/<package>[/<version>] |
| Package README | Fetch README for a package via resource URI. |
| Package downloads | Downloads from api.npmjs.org for last day/week/month. |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes, but search_npm and search_by_keywords could be confused since both are search-related. The descriptions differentiate them (general search vs. keyword/tag search), but the overlap is minor.
All tools follow a consistent verb_noun snake_case pattern (e.g., search_npm, get_package_info, compare_packages). Naming is predictable and clear.
With 9 tools, the set is well-scoped for an npm package analysis server. Each tool addresses a distinct need without being excessive.
The tool surface covers the main lifecycle of npm package research: search, info retrieval, downloads, versions, dependencies, and comparison. No significant gaps are apparent for read-only package analysis.