MCP Tools

MCP Tools

Every tool @the-i18n-kit/mcp advertises is listed below and documented on its own page, with the parameters and descriptions an MCP host receives.

These pages are generated by starting the-i18n-mcp over stdio and reading its tools/list response, so they describe what your host is handed rather than what the server declares internally. A tool that stops being advertised stops being documented.

Tools

ToolWhat it does
discoverDiscover i18n Setup
list_namespacesList Namespaces
find_empty_translationsFind Empty Translations
get_translationsGet Translations
write_translationsWrite Translations
get_missing_translationsGet Missing Translations
get_translation_statusGet Translation Status
search_translationsSearch Translations
remove_translationsRemove Translations
move_translation_keyMove Translation Key Between Layers
rename_translation_keyRename Translation Key
translate_missingTranslate Missing
translate_keyTranslate Key
find_orphan_keysFind Orphan Translation Keys
find_undefined_keysFind Used-But-Undefined Translation Keys
find_duplicate_keysFind Duplicate Translation Keys Across Layers
remove_orphan_keysRemove Orphan Keys
scaffold_localeScaffold Locale

Paired CLI Commands

@the-i18n-kit/mcp depends on @the-i18n-kit/cli and calls the same functions the commands call, so a tool and the command it pairs with read the same project and return the same result. Where you run an operation from is a matter of who is driving.

Parameters and flags are named for their surface — a tool takes targetLocales, the command takes --targets — so the command pages document the flags rather than these pages restating them.

Parameters Every Tool Accepts

projectDir appears on every tool. Each tool page documents it with the description that tool advertises, since a host validates a call against that tool's schema alone.

Diverting a Large Result

find_empty_translations, get_missing_translations, get_translation_status, search_translations, find_orphan_keys, find_undefined_keys, find_duplicate_keys, remove_orphan_keys accept outputFile. Given an absolute path, the tool writes its full JSON result there and returns a compact summary instead, so a result covering thousands of keys never enters the conversation.

Copyright © 2026