packagetrackdev-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PACKAGETRACK_SERVER | No | Server URL. | https://packagetrack.dev |
| PACKAGETRACK_API_KEY | No | Enables the project tools. Create a key at packagetrack.dev/app/keys. Also read from ~/.packagetrack/config.toml, written by `packagetrackdev login`. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| package_changesA | What the maintainers wrote about each release between two versions of a package, oldest first; a release with no notes is said to have none, and a withdrawn release is flagged. Call this before upgrading a dependency, with the installed version as |
| package_versionsA | What a package is and which versions of it exist: summary, source repository, latest stable release, and the newest releases with their dates, prerelease and withdrawn flags. Use it to pick an upgrade target or to check that a version has not been withdrawn. |
| search_packagesB | Find packages in the archive by name. Returns the matches across every registry with a one-line summary each. |
| list_projectsA | The user's projects on PackageTrack (pushed with |
| project_reportA | What PackageTrack tells the user about one of their projects: withdrawn versions in the build, each dependency that is behind with the notable lines from the newest releases it is missing, and where the full notes are. Needs a PackageTrack API key; list_projects gives the names. |
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 maps to a distinct step in the workflow: searching, inspecting versions, reading release changes, listing projects, and generating a project report. package_changes and package_versions share the same prefix and both relate to versions, so they could be confused at first glance, but the descriptions clearly separate change notes from version metadata.
The names are uniformly snake_case and readable, but the naming pattern is mixed: search_packages and list_projects follow verb_noun, while package_changes, package_versions, and project_report are noun phrases. A consistent verb_noun style such as list_package_changes and get_project_report would improve predictability.
Five tools is well within the ideal scope for a focused server, and each tool earns its place in the dependency-tracking and upgrade workflow. Nothing feels redundant or tacked on.
The toolset covers a complete workflow: find packages, inspect version status, read release notes, list the user's projects, and pull an upgrade-oriented project report. There are no obvious dead ends for the server's apparent purpose of supporting dependency review and upgrades.