Ext Ops Panel
Open dashboard
Comparison

i18n-localization vs StringLane

i18n-localization is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). StringLane is an MCP server published by thebedcoder. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacei18n-localizationStringLane
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.7
Forks (GitHub): 4 090
Stars (GitHub): 29 522
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.0
Downloads/month (npm): 897
Downloads/week (npm): 94
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

i18n-localization vs StringLane
Facti18n-localizationStringLane
Marketplaces that list it11
Stars (GitHub) (differs)29 522No figure on GitHub
Forks (GitHub) (differs)4 090No figure on GitHub
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleOn your machine (@stringlane/cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alirezarezvani/claude-skillsNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-11-032026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

i18n-localization

In its own words, on Community GitHub marketplaces:

Ship a new language without the usual breakage. Three deterministic stdlib scripts: a translation-file checker for JSON/ARB (i18next, ICU), .properties, .strings, Android strings.xml and gettext .po that blocks on missing keys, renamed placeholders, ICU syntax errors, plural/select without other, zero branches that never match and plural categories the target locale needs, from the embedded Unicode CLDR 49 table (ru few/many, ar six forms); a hardcoded-string scanner for React, Vue, Svelte and HTML that flags text and user-facing attributes outside t, concatenated translations, locale-less toLocaleString and '$' + amount; and a pseudo-locale generator (en-XA accented and expanded, ar-XB right-to-left) that keeps placeholders and ICU syntax intact. Ships cs-i18n-engineer agent, /cs-i18n-check and /cs-pseudo-locale commands and 3 cited references.

StringLane

In its own words, on Official MCP Registry:

Check, translate and fix app localization files: ARB, iOS strings, Android XML, i18next JSON.

How to run each

i18n-localization As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install i18n-localization@claude-code-skills

StringLane As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio stringlane -- npx -y @stringlane/cli mcp .

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: i18n-localization · What it can do: StringLane · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built