A
licenseNot graded
qualityA
maintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.
MIT
i18n-mcp
by robin-heat
Related Servers
Alternatives to i18n-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server for managing Rails-style localization files (YAML/JSON), enabling coding agents to read, search, write, and audit translations without hand-editing files.710 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI agents read and write locale JSON translation files directly from the conversation without loading the whole catalog into context.6 npm1ISC
- AlicenseAqualityBmaintenanceMCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.15251 npm11MIT
kilo-dev-mcp-serverofficial
AlicenseNot gradedqualityFmaintenanceAn MCP server for internationalization (i18n) tasks, providing tools to translate, move, list, and remove translation keys in JSON files for the Kilo Code extension.24MIT- FlicenseNot gradedqualityDmaintenanceMCP server for the SELISE Blocks UILM API, providing translation key management tools for Claude Code, Cursor, and any MCP-compatible client.-
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation4/5
Get-side tools (get_translation, get_translations, get_namespace_keys) are well differentiated by scope thanks to clear descriptions. However, the four audit tools (check_translation_integrity, find_untranslated_values, get_pending_translations, check_translation_quality) overlap substantially, especially get_pending_translations which is nearly a superset of check_translation_integrity and find_untranslated_values; descriptions mitigate but don't eliminate the confusion.
Naming Consistency5/5
Every tool uses snake_case with a consistent verb_noun(phrase) pattern (get_, add_, check_, find_, copy_, delete_). The one variation, get_i18n_status, still fits the schema and reads clearly.
Tool Count5/5
12 tools is well-scoped for a translation-management domain, covering reads, writes, deletion, integrity/quality audits, and status without excessive redundancy.
Completeness4/5
Core key lifecycle is covered (create/update via add_translation and add_multiple_translations, read, delete, plus quality checks), but there is no key rename/move, no bulk delete, and no namespace or locale creation/management. These are minor gaps an agent can mostly work around.