MCP Tools
Four tools, all backed by the same engine as the CLI.
translate_json
Translates a JSON string and returns the result. Best for content already in the conversation.
| Argument | Required | Description |
|---|---|---|
content | yes | The JSON to translate, as a string |
to | yes | Target language codes, comma-separated |
from | no | Source language (default en) |
provider | no | anthropic or openai; needs the matching key in the client env |
translate_file
Reads a locale file from disk, translates it, and writes one file per target language beside it. Supports incremental mode so existing translations are reused.
list_languages
Returns the language codes the engine knows names for — useful when you are unsure of a code.
check_placeholders
Compares a source file against a translation and reports any placeholder that went missing. This runs no model at all, so it is free and instant — handy in review.
Notes
- Paths are resolved relative to the working directory your MCP client launched the server in.
- Every tool preserves structure and placeholders exactly as the CLI does.
- To translate (rather than validate), set a provider key in the
envblock.