mcp-package-version

The mcp-package-version server provides tooling to fetch and verify the latest stable versions across multiple package registries. It supports an array of ecosystems including npm for Node.js, PyPI for Python, Maven Central for Java, Go Proxy, Swift Packages, AWS Bedrock models, Docker Hub and GitHub Container Registry for container images, and GitHub Actions. The server can operate in two transport modes: stdio (default) and SSE (Server-Sent Events), allowing you to integrate with various clients and orchestration systems. Each tool type is exposed as a standalone command payload that you send to the MCP server to get the latest versions or perform specific checks, for example requesting the latest versions for a set of dependencies or scanning a pyproject.toml or requirements.txt for up-to-date releases. Use the provided Tools section in the server to see the available JSON payloads for each registry.

To use the server, run the binary (or container) and send a request in the MCP format described by the Tools examples. For stdio, invoke the binary directly and pass a JSON payload to query version information. For SSE, connect to the /sse endpoint and receive streaming updates. The server is designed to be compatible with common MCP clients and can be wired into CI, editors, or chat-based assistants to ensure recommendations reference current package versions.

Prerequisites:\n- A modern Go toolchain installed (Go 1.20+ recommended)\n- Optional: Docker for container runs or access to a Go workspace with GOPATH configured\n\nInstall from source (recommended for MCP client setup):\nbash\n# Prereqs: ensure Go is installed (https://go.dev/dl/)\n\ngo version\n\n# Install the MCP server binary (build from source)\n# Navigate to the repository and build the binary (adjust module path if needed)\ngo install github.com/sammcj/mcp-package-version/v2@HEAD\n

If GOPATH is not in your PATH, provide the full path to the binary (example shown in the README):\nbash\n# If your GOPATH is /Users/you/go, the binary might be at /Users/you/go/bin/mcp-package-version\n

Run via Go build with local repo (alternative):\nbash\ngit clone https://github.com/sammcj/mcp-package-version.git\ncd mcp-package-version\nmake\n\n Run with Docker (container):\nbash\ndocker run -p 18080:18080 ghcr.io/sammcj/mcp-package-version:main\n

Configuration example for MCP client (when not using URL):\njson\n{\n "mcpServers": {\n "package-version": {\n "command": "/path/to/mcp-package-version"\n }\n }\n}\n

If you prefer to expose the server via URL (container mode), you can configure the client like this:\njson\n{\n "mcpServers": {\n "package-version": {\n "url": "http://localhost:18080"\n }\n }\n}\n

Additional tips: if using Go, ensure GOPATH/bin is in your PATH to run the binary directly by name. When running in a container, set the client URL to the container’s address and port as shown above.

Notes and tips:\n- The server focuses on helping ensure recommendations use up-to-date versions across multiple ecosystems.\n- When running in a container, you typically configure the MCP client to connect via URL rather than a local command.\n- If you customize environments or paths, ensure the MCP client has executable permissions for the mcp-package-version binary.\n- Transport options: stdio (default) is easiest for local workflows; SSE enables streaming prompts from the MCP server to clients over HTTP.\n- For Go-based deployments, remember to configure GOPATH and PATH if you install via go install.\n- Docker-based usage requires exposing the correct port (default 18080) and updating client configurations to point to the URL.\n- This server’s tooling includes examples for npm, Python, Maven, Gradle, Go, Docker, AWS Bedrock, and more, each with a payload demonstrating how to request latest versions.\n- If you encounter rate limits or registry API changes, check the registry policies or update the specific payloads to align with current APIs.