i18next MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| I18N_LOCALES_PATH | No | Path to translation files | public/locales |
| I18N_PROJECT_ROOT | No | Your project root directory | Current directory |
| I18N_DEFAULT_LANGUAGE | No | Source language | en |
| I18N_SUPPORTED_LANGUAGES | No | Comma-separated language codes | en |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_infoB | Get information about the translation project configuration and status |
| health_checkC | Perform comprehensive health check on translation files |
| validate_filesC | Validate translation files for JSON syntax and structure issues |
| list_filesB | List all translation files with their basic information |
| coverage_reportC | Generate comprehensive coverage report for translations |
| quality_analysisC | Analyze translation quality across files |
| usage_analysisC | Generate detailed usage analysis of translation keys |
| export_dataB | Export translation data in various formats |
| sync_missing_keysC | Synchronize missing translation keys across all languages from a source language, maintaining sorted structure |
| add_translation_keyA | Add a specific translation key with values to specified languages and namespaces |
| sync_from_sourceB | Sync specific missing keys from source language to target languages |
| sync_all_missingC | Comprehensive sync to add all missing keys across all languages, ensuring complete coverage |
| get_missing_keysB | Get a detailed list of missing keys by language and namespace for targeted translation work |
| scan_code_for_missing_keysC | Scan code for missing keys using the scanner integration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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.
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.
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.
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.