Skip to main content
Glama

glot

Your coding agent localizes your app. Deterministic code guarantees that nothing broken or too long lands in your catalogs.

glot translate refuses a Polish plural without few/many, a {nom} placeholder the source does not have and a German label 276px wide for a 120px button, then writes the corrected retries

The real glot translate binary. The LLM is scripted to get three strings wrong on its first pass; every refusal and message is glot's. Reproduce it, or rerun it with a real model doing the retries: docs/launch/record/refusal.sh.

npx glot-i18n init        # detect your i18n stack, write glot.toml + rules for your coding agent
npx glot-i18n i18nize     # hardcoded UI strings -> keys, components rewritten (next-intl, react-i18next)
npx glot-i18n translate   # translate only the delta; invalid output is refused, retried, never written

Or all of it in one idempotent step: npx glot-i18n localize --yes --targets fr,de (init if needed → i18nize → translate → check).

Guarantees

Checked by code on every LLM output, on glot set, in the overlay and in CI (glot check). A refused string goes back to the model with the exact reason (2 retries, then the fallback model); if it still fails, nothing is written.

Placeholders

{name}, {{name}}, tags: same set as the source, none invented, none translated. ICU, i18next and MessageFormat 2 syntax parsed.

CLDR plurals

Every category the target locale needs (pl: one, few, many, other; ar: six of them).

Glossary

glossary.toml in your repo: required and forbidden translations, do-not-translate terms.

Pixel width

glot measure records each key's box and font from your running app; translations are shaped with that font and refused if wider. glot fit shortens what already overflows.

Lockfile

glot.lock hashes source and target: only the delta is translated, and a hand edit is never overwritten without --force.

MCP for your agent

glot mcp gives Claude Code, Cursor or Codex your keys, their usages (file:line, UI role), the glossary, and tools that add strings through the same validator.

Works with the i18n library you already use, adds no runtime, bring your own LLM key (Anthropic, OpenAI, any OpenAI-compatible endpoint). MIT.

More: Docs (concepts, CLI, MCP, integrations & GitHub Action, agent skill, AI-translation provenance, FAQ & costs) · Labs (SEO, database content, emails/images, task parity, plural coverage…) · Self-hosted server (experimental) · Demo app · Architecture

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    AI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.
    7 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    AI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.
    7
    760 PyPI
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Lets a coding agent find, translate, validate and review an app's existing localization files (Android strings.xml, Apple String Catalogs, gettext) directly in the repo, supplying code usage, comments, glossary and voice notes as context. Placeholders, plural forms, escaping and markup are checked in code before any translation is written, and results land as reviewable drafts that never overwrite hand edits or approved work.
    72 npm
    1
    MIT