KAERIS i18n

KAERIS MCP server

Lets Claude Desktop, Claude Code, Cursor or any MCP client check your app's locale files and translate them into 46 languages.

pip install kaeris-mcp && claude mcp add kaeris-i18n kaeris-mcp

• Three tools work offline with no key: find the locale files in a repo, report missing keys and broken placeholders per language, list the exact keys to fix.
• Translation keeps placeholders and markup, translates only new keys with only_new, and with verify=True translates each line back to flag a changed meaning.
• 13 formats: JSON, YAML, .strings, .xcstrings, .po, ARB, Android XML, CSV, XLIFF, .properties, .resx, Fluent .ftl, Markdown.
• Same engine and kaeris.lock as the CLI, so an agent, a teammate and CI agree on what is already translated.

Plans. No key needed to try it. Free API key: 50k characters per file, 8 languages per run. Pro $19/month with 12M characters, Team/API $79/month with 60M, Lifetime $79 once with your own OpenRouter key. See kaeris.dev/pricing.

Docs · Pricing · Discussions · Status · Security

Tools

The first three tools are local-only (no network call, no cost), and kaeris_list_languages is one free API call that counts toward no limit — an agent can use all four freely to audit and understand a repo's i18n before deciding what (if anything) to translate.

Reproducible by design

kaeris_translate_file with only_new=True keeps a kaeris.lock next to your source file — the same lock the CLI writes, so an agent and a human sharing a repo stay in sync. It records a hash of every source string plus the settings that produced it: tone, glossary, app context, and the model. That means:

• Edit one string — only that string is re-translated; everything else stays byte-for-byte.
• Change tone, glossary or context — the whole locale is re-translated, never a mix of old and new.
• Change plan — every tier runs the same model (GPT-6 Luna), so upgrading does not force a re-translation. The lock records the model regardless: the day we change it, the locale is rebuilt in full instead of quietly ending up the work of two models.

Commit kaeris.lock alongside your source file so the agent, your teammates and CI all agree on what is already done.

Install

pip install kaeris-mcp

Or run it with Docker

docker build -t kaeris-mcp .

docker run -i --rm -v "$PWD:/work" -w /work kaeris-mcp

The server speaks JSON-RPC over stdin/stdout, so there is no port to expose — -i is what keeps the conversation open. Mount your project at /work and the repo-aware tools (scan_repo, status, list_missing_keys) read it directly; pass -e KAERIS_API_KEY=… to use your KAERIS key.

Configure your client

Claude Desktop — add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{

"mcpServers": { "kaeris-i18n": { "command": "kaeris-mcp", "env": { "KAERIS_API_KEY": "kaerisp_optional" } } } }

Cursor — Settings → MCP → Add, or .cursor/mcp.json:

{ "mcpServers": { "kaeris-i18n": { "command": "kaeris-mcp" } } }

Claude Code — one command:

claude mcp add kaeris-i18n kaeris-mcp

Restart the client; the KAERIS tools appear automatically.

Auth & tiers (all optional)

No key is required to try it — the free demo works out of the box.

Example prompts

• *"Translate the strings in locales/en.json into German, Ukrainian and Japanese."*
• *"Add French and Spanish translations for these buttons: Save, Cancel, Delete."*
• *"Only translate the new keys I added to en.json — don't redo the whole file."*
• *"Check this repo's i18n and tell me what's missing or broken."* (scans, then reports status — no API call)
• *"We don't have Ukrainian yet — add it."* (bootstraps a new locale via translation)

License

MIT