the-i18n-kit vs Weblate MCP by usefulapi
the-i18n-kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
the-i18n-kit is a plugin bundle for AI coding tools published by Fabian Kirchhoff. No marketplace we read lists it any more. Weblate MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Weblate MCP by usefulapi | |
|---|---|---|
| Community marketplace fabkho/nuxt-i18n-mcp | Removed on 2026-10-27 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.11.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | the-i18n-kitno longer listed · | Weblate MCP by usefulapi |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 11 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (@the-i18n-kit/mcp) | Remote server (weblate.usefulapi.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/fabkho/nuxt-i18n-mcp | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 2 | 10 |
| First seen (differs) | 2026-10-13 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of the-i18n-kit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing.
-
intlpull io.github.intlpull/intlpull
AI-powered i18n platform with 50+ tools for translations, OTA releases, and more.
-
i18n-codelens-mcp io.github.hepter/i18n-codelens-mcp
Inspect, audit and safely edit i18n locale JSON files from AI agents.
-
i18n io.github.rog0x/i18n
Locale detect, translations, plurals for AI agents
-
Internationalization and localization expert for global applications
-
AI-native i18n: live string context, validated translations, glossary for your app catalogs
What each says it does
the-i18n-kit
i18n toolkit for AI agents: MCP server, locale-file guardrails, undefined-keys gate.
Weblate MCP by usefulapi
Read Weblate projects, strings, stats and changes; translate, suggest, comment and autotranslate.
How to run each
the-i18n-kit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Weblate MCP by usefulapi As a remote MCP server
claude mcp add --transport http weblate https://weblate.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Weblate MCP by usefulapi has a remote endpoint we check. How we check endpoints
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: the-i18n-kit · What it can do: Weblate MCP by usefulapi · 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.