i18n-locale-mcp
Related Servers
Alternatives to i18n-locale-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables deterministic linting of locale files across JSON, Laravel PHP, gettext, and YAML, with no LLM or network, verifying translations for missing keys, placeholders, plural forms, glossary consistency, and stale entries.5 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to inspect multi-framework projects, detect hardcoded user-facing strings with AST precision, generate and safely apply internationalization plans, translate and validate catalogs, generate TypeScript types and pseudolocales, format translation files, and audit RTL layout issues.16813 npmMIT
- AlicenseAqualityBmaintenanceTranslation QA for i18n locale files. Deterministic validators — missing keys, placeholder drift, collapsed plurals, glossary breaches — that need no API key, plus a review tool that hands translation pairs and judging criteria back to the calling agent, so meaning-level review runs on the model your client already has. Translation with your own LLM key is optional. JSON, Flutter .arb, Apple .8Apache 2.0
- AlicenseAqualityBmaintenanceAI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.7119 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceAI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.MIT
- AlicenseNot gradedqualityBmaintenanceLets a coding agent find, translate, validate and review an app's existing localization files (Android strings.xml, Apple String Catalogs, gettext) directly in the repo, supplying code usage, comments, glossary and voice notes as context. Placeholders, plural forms, escaping and markup are checked in code before any translation is written, and results land as reviewable drafts that never overwrite hand edits or approved work.36 npm1MIT
TDQS
Scored across 5 tools
Each tool has a distinct primary purpose, but localize overlaps slightly with i18n_lint and glossary_apply because it performs post-processing. The descriptions clarify when to use each, so confusion is limited.
All names use snake_case, which is consistent, but the structural pattern varies: list_locales and pseudo_localize are verb-like, i18n_lint and glossary_apply are noun-first, and localize is a bare verb. This is mostly predictable with minor deviations.
Five tools is well-scoped for a focused i18n localization toolkit. Each tool earns its place by covering a specific stage of the localization workflow.
The surface covers locale inspection, pseudolocalization, linting, glossary enforcement, and translation, which is strong lifecycle coverage. Minor gaps exist around configuring translation providers or extracting strings from source files, but agents can work around these.