i18n-LE MCP server

i18n-LE: The Locale That Only Looks Finished Audit translation catalogues against the source locale, in one keystroke i18next, next-intl, VS Code bundles and Flutter ARB — keys and tokens, never a translated string

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

★ GitHub ·

★ Open VSX ·

★ Marketplace

What it does

Spanish shipped last week and the metrics screen has said {{periodo}} to every user since. The catalogue had every key. It parsed. The placeholder came back from machine translation with its name translated too, which compiles perfectly and renders the literal.

Open a catalogue, run i18n-LE: Audit Catalogues, and the set it belongs to is audited against the source locale: keys a locale is missing or has too many of, placeholders dropped or renamed in translation, constructs from another library's convention, values left empty, keys defined twice, and a path that is an object in one locale and a string in another. The report opens beside the editor. From the Explorer, run it on any folder. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).

• Before a release — is this locale shippable, or does it only look like it is?
• After machine translation — {{timeframe}} that came back as {{periodo}}, caught by its token names
• Reviewing a translator's pull request — the keys that changed shape, without reading the translations

The report never contains a translated string. It names keys, placeholder tokens, counts and shapes; an untranslated string is proved by being byte-identical to the source, not by being shown. It rewrites nothing.

Install

It works out which library you use first

Shortened. The full README is on GitHub.