F
licenseNot graded
qualityB
maintenanceEnables AI agents to read and write JSON translation files (i18n, i18next, react-i18next) via the Model Context Protocol.
20 npm
2
-
i18next MCP Server
by gtrias
Related Servers
Alternatives to i18next MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables translation of JSON i18n files to multiple languages using various AI providers (Google Gemini, OpenAI, Ollama/DeepSeek) with intelligent caching and deduplication.20 npm5-
- AlicenseAqualityAmaintenanceEnables AI agents to inspect, audit and safely edit locale JSON files across flat, nested, and namespaced layouts without loading whole files into the model context, with compact token-efficient reads and write paths that cannot drop keys or overwrite silently. Ships ten tools plus slash-command prompts for project info, key search, reference lookup, translation upserts, and missing-translation audits.1044 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables localization of React, Next.js, and Vue apps from an AI assistant by managing projects, languages, translations, glossaries, style guides, and GitHub repository integration.MIT
POEditor MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage POEditor translation projects, including terms, translations, contributors, languages, and glossaries, with automatic translation, Figma round-trips, and exports to any supported format.1MIT- AlicenseAqualityDmaintenanceEnables automatic discovery and fast searching of translation files in projects, supporting partial/exact key-value matching with file watching and multiple translation file formats.2MIT
TDQS
C2.9/5.0
Scored across 14 tools
Disambiguation2/5
Multiple sync tools (sync_missing_keys, sync_from_source, sync_all_missing) have nearly identical descriptions, making it difficult to choose between them. health_check, quality_analysis, and validate_files also overlap somewhat in their focus on analyzing file health.
Naming Consistency3/5
All tool names use snake_case, but the pattern is inconsistent: some are verb_noun (get_project_info, list_files, add_translation_key) while others are noun-based (health_check, quality_analysis, coverage_report). The three sync tools are confusingly similar in naming.
Tool Count4/5
14 tools is within the typical 3-15 range and appropriate for the scope of i18next translation management. However, the redundant sync tools could be consolidated, making the count feel slightly padded.
Completeness2/5
The toolset lacks basic update and delete operations for translation keys, and there is no import functionality. It is heavily skewed toward analysis and adding missing keys, leaving gaps in the full lifecycle management of translations.
Maintenance
ActivityInactive
ResponsivenessNo issues