F
licenseNot graded
qualityB
maintenanceEnables AI agents to read and write JSON translation files (i18n, i18next, react-i18next) via the Model Context Protocol.
184 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.14 npm5-
- FlicenseAqualityDmaintenanceEnables automatic discovery and fast searching of translation files in projects, supporting partial/exact key-value matching with file watching and multiple translation file formats.2-
- AlicenseAqualityAmaintenanceEnables interaction with the SimpleLocalize API to manage translation keys, languages, and tags. It allows users to streamline their localization workflow by creating, updating, and retrieving translation data directly through MCP-compatible AI assistants.4729 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects AI tools to Verblaze localization projects, enabling management of translations, languages, screens, and project resources through natural language interactions.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Crowdin translation projects with tools for listing projects, files, source strings, translations, and performing bulk search-and-replace operations.MIT
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