Scan a repository to identify its i18n setup: locale files, base and target languages, and framework. Use the results to pinpoint where to audit or add translations.
MIT
458,158 tools. Updated 2026-08-14 23:05
"i18next" matching MCP tools:
- Scan your project for locale files, detect the i18n framework, and get a structured list of available translations with key counts.MIT
- Find new or updated translation keys from your project changes, deduplicate them, and return them with source-derived prefixes. Optionally specify a git ref for comparison.
- Add missing translation keys to i18next files, specifying languages, namespaces, and nested paths, with optional overwrite and backup.MIT
- Discover translation files and their details, filtering by language or namespace.MIT
- Retrieve translation project configuration and status to assess localization coverage and manage i18next files effectively.MIT
Matching MCP Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to manage i18next translation files, including adding keys, syncing missing translations, and analyzing coverage.145912MIT
- Flicense-qualityCmaintenanceEnables AI agents to read and write JSON translation files (i18n, i18next, react-i18next) via the Model Context Protocol.121
- Export translation data in JSON, CSV, XLSX, or Gettext formats for sharing or integration.MIT
- Synchronize missing translation keys from the source language to selected target languages, specifying which keys to sync and optionally copying source values as placeholders.MIT
- Identify untranslated i18n keys across languages and namespaces. Focus translation efforts on exactly what's missing.MIT
- Checks translation files for JSON syntax and structural problems, with an option to automatically repair detected issues.MIT
- Identify missing translations in i18next files by generating a coverage report, optionally scoped to languages and namespaces.MIT
- Analyze translation quality across i18next files. Identify missing, incomplete, or inconsistent translations, with optional filtering by language or namespace.MIT
- Scan source code to analyze translation key usage. Identify used, unused, and missing keys to update i18next translation files.MIT
- Synchronize missing translation keys across languages by copying from a source language, with dry-run, placeholder, backup, and namespace options.MIT
- Sync all missing translation keys across every language to fill gaps and ensure complete coverage.MIT
- Scan source code directories to find missing i18next translation keys and list them for addition.MIT
- Check translation files for missing or inconsistent keys across languages and namespaces, highlighting coverage gaps to ensure complete localization.MIT