i18next

This MCP server provides translation management capabilities for i18next projects, enabling AI assistants and automation tools to interact with translation files directly. It exposes a suite of core tools for project analysis, translation key management, file operations, and quality checks. You can query project information, scan for missing keys, validate JSON translation files, export data, and generate analyses like coverage, usage, and quality reports. To use it with Cursor or other MCP clients, configure the server in your MCP settings so the client can invoke these tools via the defined commands. The core workflow typically involves inspecting translation files under your locales directory, adding or syncing keys across languages, and exporting translations for downstream processes or formats.

Prerequisites:

• Node.js and npm (or npx available via npm 5.2+)
• Internet access to fetch the MCP server package via npx

Installation and setup steps:

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v
2. Test running the MCP server with npx (no local install required): npx i18next-mcp-server@latest --help
3. If you prefer to install locally, you can add the package to your project: npm install --save-dev i18next-mcp-server npx i18next-mcp-server@latest --help
4. Prepare Cursor (or your MCP client) configuration using the example in the repository README. Save the configuration in your Cursor settings or the MCP client config file to enable the i18next translation workflow.
5. If you plan to run the server repeatedly, consider using the recommended command from the mcp_config example and ensure the environment variables are set to match your project layout.

Tips and common considerations:

• Environment variables should reflect your actual project structure. Typical defaults are I18N_PROJECT_ROOT as your project root, I18N_LOCALES_PATH as public/locales, I18N_DEFAULT_LANGUAGE as en, and I18N_SUPPORTED_LANGUAGES as a comma-separated list like en,es,fr.
• The server expects a standard i18next project layout with translation JSON files organized by language under the locales path (e.g., public/locales/en/translation.json).
• When using Cursor, ensure your MCP configuration references the correct command and arguments for npx and that the env variables point to your local project files to enable seamless translation management.
• For production usage, consider pinning the MCP server version (e.g., i18next-mcp-server@vX.Y.Z) to avoid breaking changes from upstream releases.
• If you run into JSON validation errors while using validate_files, check for trailing commas and ensure all translation JSON files are well-formed before performing exports or imports.