MCP Package Hero
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_versionA | Get the latest stable version of a package. |
| get_latest_versions_batchB | Get latest versions for multiple packages at once. |
| rate_packageA | Get a comprehensive quality rating for a package. This tool analyzes multiple dimensions of package quality including:
|
| get_llms_txtB | Get llms.txt documentation file for a package. llms.txt is an emerging standard for providing LLM-friendly documentation. This tool fetches llms.txt files from package repositories, homepages, or documentation sites. |
| create_llms_txtB | Generate an llms.txt file for your project. Creates a standardized llms.txt file by scanning your project directory for documentation files and generating structured markdown. |
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 has a clear, distinct purpose: generating llms.txt, getting package version (single/batch), fetching llms.txt, and rating package quality. No overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (create_llms_txt, get_latest_version, etc.), making them predictable and easy to understand.
With 5 tools, the server is well-scoped for its purpose - providing package metadata, llms.txt generation, and quality ratings. Neither too sparse nor excessive.
The tool set covers key operations: version lookup (batch and single), documentation (fetch and generate), and quality assessment. A minor gap is the lack of basic package info retrieval (description, homepage), but the core workflows are covered.