Skip to main content
Glama
Sign In
i18next MCP Server

i18next MCP Server

by gtrias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

i18next MCP Server

npm version License: MIT

A Model Context Protocol (MCP) server that provides translation management capabilities for i18next projects, enabling AI assistants like Cursor to directly interact with translation files.

🚀 Quick Setup

The easiest way to use this MCP server is with npx. No installation required:

npx i18next-mcp-server@latest --help

Related MCP server: i18n-tools-mcp

🔧 Cursor Configuration

Add this to your Cursor MCP settings:

{
  "mcpServers": {
    "i18next-translation": {
      "command": "npx",
      "args": ["-y", "i18next-mcp-server@latest"],
      "env": {
        "I18N_PROJECT_ROOT": "/path/to/your/project",
        "I18N_LOCALES_PATH": "public/locales",
        "I18N_DEFAULT_LANGUAGE": "en",
        "I18N_SUPPORTED_LANGUAGES": "en,es,fr"
      }
    }
  }
}

For detailed setup instructions, see CURSOR_SETUP.md.

📁 Expected Project Structure

your-project/
├── public/locales/          # Translation files
│   ├── en/
│   │   ├── common.json
│   │   └── navigation.json
│   ├── es/
│   │   ├── common.json
│   │   └── navigation.json
│   └── ...
└── src/                     # Your source code

🛠️ Available Tools

Core Tools

  • get_project_info - Get project configuration and statistics

  • health_check - Analyze translation file health and completeness

  • scan_code_for_missing_keys - Find missing translation keys in your code

Key Management

  • add_translation_key - Add new translation keys

  • sync_missing_keys - Sync missing keys between languages

  • get_missing_keys - List missing keys by language

File Operations

  • list_files - List all translation files

  • validate_files - Validate JSON syntax

  • export_data - Export translations to various formats

Analysis

  • coverage_report - Translation coverage statistics

  • usage_analysis - Find unused translation keys

  • quality_analysis - Analyze translation quality

🔧 Environment Variables

Variable

Description

Default

I18N_PROJECT_ROOT

Your project root directory

Current directory

I18N_LOCALES_PATH

Path to translation files

public/locales

I18N_DEFAULT_LANGUAGE

Source language

en

I18N_SUPPORTED_LANGUAGES

Comma-separated language codes

en

🧪 Development

git clone https://github.com/gtrias/i18next-mcp-server.git
cd i18next-mcp-server
npm install
npm run build
npm test

📝 License

MIT License - see LICENSE for details.

🔗 Links

Available Tools

14 tools
add_translation_keyA

Add a specific translation key with values to specified languages and namespaces

Inputs: key (required), translations (required), overwrite, namespaces, +1 more.

coverage_reportC

Generate comprehensive coverage report for translations

Inputs: languages, namespaces.

export_dataB

Export translation data in various formats

Inputs: format (required), languages, namespaces.

get_missing_keysB

Get a detailed list of missing keys by language and namespace for targeted translation work

Inputs: format, namespaces, sourceLanguage, targetLanguages.

get_project_infoB

Get information about the translation project configuration and status

Inputs: no named parameters.

health_checkC

Perform comprehensive health check on translation files

Inputs: summary, detailed, languages, namespaces.

list_filesB

List all translation files with their basic information

Inputs: language, namespace.

quality_analysisC

Analyze translation quality across files

Inputs: languages, namespaces.

scan_code_for_missing_keysC

Scan code for missing keys using the scanner integration

Inputs: sourceCodePaths.

sync_all_missingC

Comprehensive sync to add all missing keys across all languages, ensuring complete coverage

Inputs: dryRun, placeholder, createBackup.

sync_from_sourceB

Sync specific missing keys from source language to target languages

Inputs: keys (required), targetLanguages (required), copyValues, namespaces, +2 more.

sync_missing_keysC

Synchronize missing translation keys across all languages from a source language, maintaining sorted structure

Inputs: dryRun, namespaces, placeholder, createBackup, +2 more.

usage_analysisC

Generate detailed usage analysis of translation keys

Inputs: sourceCodePaths.

validate_filesC

Validate translation files for JSON syntax and structure issues

Inputs: fix.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • i18n-codelens-mcp

      hepter
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to inspect, audit and safely edit locale JSON files across flat, nested, and namespaced layouts without loading whole files into the model context, with compact token-efficient reads and write paths that cannot drop keys or overwrite silently. Ships ten tools plus slash-command prompts for project info, key search, reference lookup, translation upserts, and missing-translation audits.
      10
      60 npm
      MIT