I18n
This server gives Claude native i18n operations through six tools that cover the typical localization workflow. You can detect languages in text with confidence scores, extract hardcoded strings from JSX/HTML/JS that need translation keys, analyze translation JSON files for missing keys and interpolation mismatches across locales, generate CLDR plural rules for 15+ languages, and format numbers, currencies, dates, and relative times using Intl APIs. Reach for this when you're internationalizing a codebase and want Claude to audit your translation files, suggest i18n keys for strings it finds, or help you understand why Russian needs four plural forms while Japanese needs one.
- tools
- 5
- transport
- STDIO
- last updated
- Mar 22, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
detect_localeDetect the language and locale of a given text string. Returns the detected language code (BCP 47), language name, writing script, confidence score (0-1), and alternate language candidates.
Detect the language and locale of a given text string. Returns the detected language code (BCP 47), language name, writing script, confidence score (0-1), and alternate language candidates.
No parameter schema in public metadata yet.
extract_i18n_keysExtract hardcoded user-facing strings from source code that should be internationalized.
Extract hardcoded user-facing strings from source code that should be internationalized.
No parameter schema in public metadata yet.
analyze_translationsAnalyze translation JSON files for consistency across locales.
Analyze translation JSON files for consistency across locales.
No parameter schema in public metadata yet.
plural_rulesGenerate plural form categories for a given locale following CLDR rules.
Generate plural form categories for a given locale following CLDR rules.
No parameter schema in public metadata yet.
format_localeFormat numbers, currencies, dates, and relative times for any locale using the Intl APIs.
Format numbers, currencies, dates, and relative times for any locale using the Intl APIs.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
@rog0x/mcp-i18n-tools
Internationalization and localization tools for AI agents, exposed as an MCP (Model Context Protocol) server.
Tools
detect_locale
Detect the language and locale of a given text string. Returns the detected language code (BCP 47), language name, writing script, confidence score (0-1), and alternate language candidates.
Supported languages: English, Spanish, French, German, Portuguese, Italian, Russian, Japanese, Korean, Chinese, Arabic, Hindi, Thai, Greek, Hebrew.
extract_i18n_keys
Extract hardcoded user-facing strings from source code that should be internationalized. Finds strings in:
- JSX/TSX attributes (
title,placeholder,label,alt,aria-label, etc.) - HTML template text and attributes
console.log/console.warn/console.errorcallsthrow new Error(...)messagesalert()/confirm()/prompt()dialogs- Variable assignments with i18n-relevant names (
message,label,title, etc.)
Returns each string with its line/column, surrounding context, pattern type, and a suggested i18n key.
analyze_translations
Analyze translation JSON files for consistency across locales. Detects:
Details
- Repository
- github.com/rog0x/mcp-i18n-tools
- Package
@rog0x/mcp-i18n-tools- Transport
- STDIO
- Registry
- MCP registry, active