Home / MCP / Package Version MCP Server

Package Version MCP Server

Provides tools to fetch latest stable versions from npm, PyPI, Maven, Go, Swift, AWS Bedrock, Docker Hub, and GitHub registries for up-to-date package recommendations.

118stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "package_version_http": {
            "url": "http://localhost:18080"
        }
    }
}

You run the Package Version MCP Server to fetch and compare the latest stable versions from multiple package registries. This helps you ensure your project dependencies stay current across languages and ecosystems, including npm, PyPI, Maven, Go, Swift, AWS Bedrock, Docker Hub, and GitHub Container Registries. The server exposes both a local stdio interface and a remote HTTP endpoint for flexible integration with your MCP client workflows.

How to use

You can connect to the Package Version MCP Server in two ways: a local stdio interface or a remote HTTP endpoint. For local usage, run the server as a process and interact with it through its standard input/output. For remote usage, start the server in a container or on a host and connect via the provided HTTP URL.

How to install

Prerequisites: a modern Go toolchain installed on your development machine.

Option A: Install the binary with Go Gent: use the Go toolchain to install the MCP Package Version server.

go install github.com/sammcj/mcp-package-version/v2@HEAD

Configure your MCP client to use the stdio or HTTP endpoint below.

Option A: Run as a local stdio server

Start the server locally and connect via the stdio transport. The command shown runs the MCP server process directly.

mcp-package-version

Option B: Run as an HTTP server (container or host)

Run the server so it exposes an HTTP endpoint for remote clients. You can connect to it using the base URL shown below.

mcp-package-version --transport sse --port 18080 --base-url "http://localhost:18080"

Configure the MCP client

If you are using the HTTP server, point your MCP client to the URL where the server is hosted, for example http://localhost:18080. If you are using the local stdio setup, provide the path to the binary you started in the stdio configuration.

Docker usage

You can run the server in a container to simplify deployment. Pull the image and run it on a host with the desired port mapping.

docker pull ghcr.io/sammcj/mcp-package-version:main
docker run -p 18080:18080 ghcr.io/sammcj/mcp-package-version:main

Available tools

check_npm_versions

Check the latest versions of NPM packages specified in your dependencies and enforce constraints on major versions as needed.

check_python_versions

Check the latest versions of Python packages from requirements.txt and ensure compatibility with your project.

check_pyproject_versions

Check the latest versions of Python packages in pyproject.toml dependencies and optional/dev-dependencies.

check_maven_versions

Check the latest versions of Java packages from Maven coordinates and update dependency declarations.

check_gradle_versions

Check the latest versions of Java packages from Gradle configurations and ensure lockfile consistency.

check_go_versions

Check the latest versions of Go modules listed in go.mod and verify compatibility.

check_docker_tags

Check available tags for Docker images to keep container references up to date.

check_bedrock_models

List and search AWS Bedrock AI models to identify current offerings and versions.

get_latest_bedrock_model

Retrieve the latest Claude Sonnet model or equivalent current model from Bedrock.

check_swift_versions

Check the latest versions of Swift packages and package dependencies.

check_github_actions

Check the latest versions of GitHub Actions used in workflows and actions repos.