Kaeris MCP Server

MCP server for KAERIS i18n — AI-native localization for Claude Desktop, Cursor & agents. Exposed over MCP by the kaeris mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

AI-native localization over the Model Context Protocol. Give Claude Desktop, Cursor, Claude Code (or any MCP client) the ability to translate your app's strings into 46 languages — placeholder-safe, format-aware, incremental, with built-in Translation QA.

Its toolset

Everything the assistant can do here goes through one of these:

• kaeris_scan_repo — Discover a repo's i18n setup: locale files found, base language, target languages, framework guess
• kaeris_status — Completeness/health per target locale — missing keys, extra keys, placeholder mismatches, plus the quality detectors that gate a merge in CI: number
• kaeris_list_missing_keys — The exact missing/broken keys (with source text) for one target locale, so an agent knows exactly what to fix
• kaeris_list_languages — List all supported target languages
• kaeris_translate — Translate inline strings → per-language results, with QA (placeholder-loss & UI-overflow flags; verify=True back-translates to check meaning)
• kaeris_translate_file — Translate a file on disk (JSON/YAML/.strings/.po/ARB/XML/CSV/XLIFF/.properties/.resx/.ftl), optional incremental — reproducible via kaeris.lock
• kaeris_add_language — Bootstrap a brand-new target locale by translating the whole source file into it

Adding it to your client

The server ships on PyPI as kaeris-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need 3 environment variables: KAERIS_API_KEY, KAERIS_OPENROUTER_KEY, KAERIS_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Kaeris's toolset — kaeris_scan_repo, kaeris_status, kaeris_list_missing_keys and 4 more — is a fair guide to whether it matches your workflow. It is maintained by KAERIS; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kaeris mcp server does with a few real requests.