Units-LE MCP server

Units-LE: One Quantity, One Unit Find every quantity in a document — durations, sizes, percentages, frequencies — with its value in one base unit, and refuse the ambiguous ones by name YAML · TOML · JSON · INI · dotenv · CSV · and anything else, scanned as text

Useful? A star or rating is how other developers find it —

★ GitHub ·

★ Open VSX ·

★ Marketplace

What it does

timeout: 30s in one service and timeout: 30000 in another are the same number of milliseconds, and nothing about the text says so. memory: 1GB and memory: 1GiB differ by 7% and look identical at a glance.

Run Units-LE: Extract Quantities and every quantity in the active document — a number welded to a unit — opens in a report beside the editor: as the document wrote it, in one base unit so two of them can be compared, with its line, column and key path. A quantity it cannot read unambiguously keeps its row and gets a reason instead of a guess. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).

• Before a migration — every timeout and memory limit in a values file, in milliseconds and bytes
• Reviewing a config change — the 500m that means minutes to one reader and millicores to another
• Against a runbook or a retention policy — the limit the document states, checked against the one the config sets
• Across a project — every file that holds a quantity, and how many, in one table

It never rewrites a document, and never guesses.

Install

A refusal is a finding

This is the whole product. Any tool can multiply 30s by a thousand; what makes this one usable in a review is that it will not pretend.

Shortened. The full README is on GitHub.