Versions LE logo

Versions LE

Compare dependency and toolchain constraints across repository manifests through MCP.

Install Versions LE

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "versions-le": {
      "command": "npx",
      "args": [
        "-y",
        "versions-le-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y versions-le-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

Versions-LE exposes repository-wide version constraint analysis through the `compare_versions` MCP tool over stdio. It reads supported package, Cargo, Python, Go, and GitHub workflow files, then reports conflicting, unsatisfiable, malformed, prerelease, MSRV, and floating constraints with their source locations. Reach for it when reviewing monorepos, dependency upgrades, or CI toolchain drift without modifying files or resolving dependency graphs. Run it with `npx versions-le-mcp` from an MCP-compatible client.

Use cases

  • Compare dependency requirements across monorepo packages
  • Find unsatisfiable constraints before a release
  • Check CI toolchains against declared Rust minimum versions
  • Review whether a dependency bump reached every manifest
  • Inspect version drift through an MCP agent

Key features

  • Exposes `compare_versions` over stdio
  • Reads package.json, Cargo.toml, pyproject.toml, go.mod, and GitHub workflows
  • Detects conflicting and disjoint version constraints
  • Reports Rust MSRV and CI toolchain mismatches
  • Explains unsupported comparisons through refusals
  • Leaves repository files unchanged

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 13d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · versions-le-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How Versions LE works

What Versions-LE does

Versions-LE compares version requirements across a repository as a single set. It can inspect package.json, Cargo.toml, pyproject.toml, go.mod, and workflow files under .github/workflows. The analysis covers dependency declarations, selected runtime or toolchain settings, package manager metadata, Cargo workspace and target variants, Go directives, and GitHub Actions references and version inputs.

The result groups each drifted dependency into one finding and includes every file, key, and constraint involved. It distinguishes a mere difference in requirements from a genuinely unsatisfiable pair. Reports also identify values deliberately excluded from comparison and explain the refusal reason.

Six finding types are available: disjoint-constraint, malformed-constraint, constraint-conflict, msrv-mismatch, prerelease-in-production, and floating-pin. Range compatibility uses interval arithmetic rather than string comparison, so equivalent spellings are not automatically treated as conflicts.

How it works

The MCP server runs the same comparison engine as the command-line tools and exposes it through the compare_versions tool. The stdio transport lets an MCP agent invoke an analysis against a repository tree. The engine examines declared requirements rather than lockfiles or the dependency graph, and it does not contact package registries or other network services.

Comparisons stay within an ecosystem. npm, Cargo, Python, and Go requirements with the same package name are not assumed to refer to the same package. The MSRV check is a separate bridge between declared Rust minimums and CI toolchain pins.

Unsupported syntax is excluded instead of approximated. Examples include unsupported Python, npm, Cargo, and CI constraint forms, ambiguous workflow version expressions, and multiple versions of one CI tool installed by separate jobs. The report records these decisions as refusals. Repository scanning skips node_modules, vendor, and .git, while .github is included.

Setup and configuration

Install and launch the MCP package with Node.js and npm:

Terminal
npx versions-le-mcp

For Claude Code, register the stdio server with:

Terminal
claude mcp add versions-le -- npx -y versions-le-mcp

VS Code 1.101 and later can receive compare_versions through the Versions-LE extension's agent mode. The extension is also available for Cursor, VSCodium, and Windsurf through Open VSX. The repository also provides separate Rust and Node command-line distributions for terminal or CI use, but those are distinct from the MCP package.

Tools and capabilities

  • Compare dependency constraints across supported manifests.
  • Detect unsatisfiable ranges with disjoint-constraint findings.
  • Report differing requirements without conflating them with unsatisfiable ranges.
  • Check Rust minimum-version declarations against CI toolchain pins.
  • Flag malformed constraints, production prerelease requirements, and floating pins.
  • Show source files, keys, constraints, and explicit comparison refusals.

The server is read-only. It does not edit, pin, update, or automatically select a version. It also does not determine which versions exist, whether releases are yanked, or what a dependency resolver would choose.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Versions LE

Versions-LE is an MCP server that connects AI agents to repository manifest and GitHub workflow analysis through the `compare_versions` tool. It compares dependency constraints, CI toolchain versions, and Rust minimum-version declarations across supported files, reporting conflicts, unsatisfiable ranges, malformed values, and explicit comparison refusals over stdio.

Run `npx versions-le-mcp` to launch it over stdio. For Claude Code, use `claude mcp add versions-le -- npx -y versions-le-mcp`. The package is distributed through npm and is intended for MCP agents.

Yes, Versions-LE works with Cursor through its Open VSX extension. The extension provides the comparison experience in Cursor, while the MCP package can be launched separately with `npx versions-le-mcp` for an MCP agent.

Versions-LE reads `package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`, and `.github/workflows/*.yml`. It examines supported dependency, runtime, toolchain, package manager, workspace, target, and workflow version fields.

No, Versions-LE is read-only and does not edit manifests, pin versions, or update dependencies. It reports the sites and requirements involved so a developer can decide how to resolve the drift.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVersions LE AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/versions-le?style=directory)](https://allmcps.com/mcp/versions-le)
HTML Embed
<a href="https://allmcps.com/mcp/versions-le"><img src="https://allmcps.com/api/badge/versions-le?style=directory" alt="Versions LE on AllMCPs" /></a>