packagetrackdev-mcp
OfficialPackageTrack MCP gives coding agents package release history and project dependency reports.
Look up package versions across PyPI, npm, crates.io, Packagist, NuGet, pub.dev, Go, and Maven Central, including summaries, repositories, dates, prerelease/withdrawn flags, and search.
Fetch release notes or changes between two versions, with paging, truncation controls, and prerelease filtering.
With
PACKAGETRACK_API_KEY: list PackageTrack projects, report withdrawn/outdated dependencies with notable release-note lines, and import/update projects from a lock file or explicit names/versions.Auto-update at startup and provide update status/doctor guidance.
Provides release history for npm packages, including available versions, prerelease and withdrawn flags, and changelog-style differences between version ranges.
Provides release history for NuGet packages, including available versions, prerelease and withdrawn flags, and changelog-style differences between version ranges.
Provides release history for Packagist packages, including available versions, prerelease and withdrawn flags, and changelog-style differences between version ranges.
Provides release history for PyPI packages, including available versions, prerelease and withdrawn flags, and changelog-style differences between version ranges.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@packagetrackdev-mcp Upgrade httpx to the newest release and tell me what changed since 0.24.1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
packagetrackdev-mcp
Model Context Protocol server for PackageTrack. Gives coding agents the release history of packages on PyPI, npm, crates.io, Packagist, NuGet, pub.dev, Go and Maven Central: what changed between two versions, which versions exist, which have been withdrawn.
Install
macOS and Linux:
curl -fsSL https://packagetrack.dev/install.sh | shWindows (PowerShell):
irm https://packagetrack.dev/install.ps1 | iexInstalls uv if needed, then this server and the
packagetrackdev CLI
as uv tools, each checked against its published SHA256 first. On Windows,
close the coding agent that runs this server before installing over it:
Windows keeps a running program's files locked. To reinstall or update, run
the same command again. The checked wheels stay in ~/.packagetrack/wheels:
uv records the file it installed from, and uv tool upgrade --all reads it
again.
Limits: the checksum covers this package's own wheel. Its dependencies (the
MCP SDK and what it needs) are downloaded by uv from PyPI and rest on
PyPI's own checks, not on ours.
Where scripts are blocked, or to install only the server, follow
the steps by hand: download the
file, check its SHA256 yourself, install it with uv.
Requires Python 3.11+.
Related MCP server: package-registry-mcp
Configuration
Claude Code:
claude mcp add -s user packagetrackdev -- packagetrackdev-mcpClaude Desktop (claude_desktop_config.json), Cursor, Windsurf and other
clients with an mcpServers map:
{
"mcpServers": {
"packagetrackdev": {
"command": "packagetrackdev-mcp"
}
}
}VS Code (mcp.json) uses servers instead of mcpServers.
Optional environment variables:
Variable | Description |
| Enables the project tools. Create a key at packagetrack.dev/app/keys. Also read from |
| Server URL. Default: |
| Set to |
Tools
Tool | Description | Key |
| Release notes for every version between | no |
| Summary, source repository, latest stable version and recent releases with prerelease and withdrawn flags. | no |
| Search the archive by name. | no |
| Projects pushed with | yes |
| Withdrawn versions and outdated dependencies in one project, with the notable release-note lines. | yes |
| Push a project: reads a lock file on your machine ( | yes |
A package the archive does not hold yet is fetched on request; ask again after a minute.
Example prompt:
Upgrade httpx to the newest release and tell me what changed since 0.24.1Agents do not always reach for tools on their own. Adding one line to
CLAUDE.md or .cursorrules helps:
Before upgrading a dependency, call packagetrack's package_changes with the installed and target versions.Updates
The server updates itself when it starts. Before any tool runs it asks
https://packagetrack.dev/cli/versions.json for the newest release. If that
release is newer, the server downloads it, checks its SHA256, unpacks it
under ~/.packagetrack/mcp/ and runs it. Nothing installed is overwritten,
so this works the same on Linux, macOS and Windows.
If the site cannot be reached within a few seconds, or the download fails, the installed release starts. After a lost connection the server waits an hour before asking again. A release that needs newer dependencies than the installed ones is not taken; run the install script again to get it.
packagetrackdev-mcp --version shows the installed release and, when an
update is the one that runs, that one too: 0.2.0 (active: 0.2.1).
A server that is already running keeps its release until the coding agent
restarts it. When a newer release is waiting, or the newest one could not
start here, tool replies end with a short note. The update_status tool
says what to do, reading local files only; packagetrackdev-mcp doctor
says the same in a terminal. When only the install script can fix it,
both show the install command, for the user to run.
Updates are off for a server pointed at another PACKAGETRACK_SERVER, for
an editable install, and with PACKAGETRACK_NO_AUTO_UPDATE=1, which also
returns to the installed release.
Limits: the checksum covers this package's own wheel, and its dependencies
come from PyPI through uv. Releases are not signed: the checksum comes
from the same site as the wheel. Releases on this computer are trusted as
far as your user account is; on macOS and Linux a release folder that
another user owns or can write to is skipped.
Uninstall
uv tool uninstall packagetrackdev-mcp packagetrackdev
claude mcp remove packagetrackdevThen delete ~/.packagetrack/wheels (%USERPROFILE%\.packagetrack\wheels
on Windows), the checked wheels uv installed from, and
~/.packagetrack/mcp, the updates the server downloaded. Uninstall first:
while a tool is installed, uv tool upgrade --all reads its wheel there. On
Windows, close the coding agent before uninstalling. The rest of
~/.packagetrack holds your settings and API key (config.toml); delete
the whole folder to remove everything.
Privacy
A tool call sends package names and version strings, plus the project name
for import_project. A lock file is read on your machine; no code, file
contents, file paths or repository names leave it. The server stores nothing
and calls no model.
Each start also sends one request to packagetrack.dev for the newest
version number, unless updates are turned off.
Debugging
Run the server under the MCP Inspector to call tools by hand:
npx @modelcontextprotocol/inspector packagetrackdev-mcpDevelopment
uv sync
uv run pytestLicense
MIT
Available Tools
5 toolslist_projectsA
The user's projects on PackageTrack (pushed with packagetrackdev push): how many dependencies each has, how many the archive could compare, and how many are behind or withdrawn. Needs a PackageTrack API key.
Inputs: no named parameters. Returns: result
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 since and the target as until (omit until for everything up to the newest release). Long ranges are paged and long notes are cut; the answer says how to get the rest, and max_chars raises the cut for one note.
Inputs: name (required), since (required), ecosystem (required), until, +2 more. Returns: result
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.
Inputs: name (required), ecosystem (required). Returns: result
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.
Inputs: name (required). Returns: result
search_packagesB
Find packages in the archive by name. Returns the matches across every registry with a one-line summary each.
Inputs: query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Real-time package and vulnerability data (Python, npm, Cargo, Go, and more) for AI coding agents.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to retrieve the latest stable versions of packages and tools across multiple ecosystems, preventing outdated dependency versions in generated code.4187 PyPI9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve detailed package information from multiple package registries (NPM, crates.io, NuGet, PyPI, Go).3,695 npmMIT
- AlicenseAqualityBmaintenanceProvides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.666 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve maintainer-written release notes and compare installed versus target dependency versions, search packages, and report on projects pushed to a dashboard.MIT