$ loading_
Manage i18next translation files, sync missing entries, and analyze localization coverage.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "i18next MCP Server" yet — see the docs or source repo.
Add these translation keys to an i18next project: common.save, common.cancel, and profile.edit. Update the zh-CN and en locale files with matching text while preserving the current JSON structure and naming style.
Updated locale JSON content with the new keys and matching Chinese and English translations.
Compare the i18next translation files in locales/en and locales/ja, find keys missing in ja but present in en, fill them with Japanese translations based on the English text, and list which keys were added.
Completed Japanese locale content plus a list of filled missing keys.
Analyze translation coverage for the current i18next project by comparing the en, fr, and de locale files. Report total keys, missing keys, coverage percentages, and identify the namespace with the largest gaps.
A coverage report showing per-language statistics and the areas that should be prioritized for completion.
Let AI manage app translation files efficiently without loading whole locale files.
Translate text and detect languages for fast multilingual content handling.
Provides translation services for fast text conversion across multiple languages.
Automatically translates Portuguese and English conversations to reduce LLM interaction costs.
Translate between Manchu and Chinese with morphology-aware enhanced machine translation.
Manage Redmine projects, issues, time logs, wiki, and files via MCP.