glot
Provides a GitHub Action that validates catalogs, translates the delta, commits catalogs and the lockfile to pull request branches, and keeps a PR comment updated with coverage, issues, and cost.
Works with i18next catalogs, validating i18next syntax, placeholders, plural categories, and glossary terms while translating missing or stale strings.
Supports Ollama as an OpenAI-compatible local endpoint for running translations without relying on external API keys.
Integrates with OpenAI and OpenAI-compatible endpoints as an LLM provider for translations, configurable via the OpenAI API key.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
glot
Your coding agent localizes your app. Deterministic code guarantees that nothing broken or too long lands in your catalogs.

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 writtenOr 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 |
|
CLDR plurals | Every category the target locale needs ( |
Glossary |
|
Pixel width |
|
Lockfile |
|
MCP for your agent |
|
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
This server cannot be deployed
Maintenance
Related MCP Connectors
Localize iOS and Android apps: coverage, missing strings, glossary-aware AI drafts and file sync.
Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
Agentic localization for documents and media, with quality checks and optional human review.
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-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 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.125 npm2MIT
- AlicenseAqualityBmaintenanceAI 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.7760 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceLets 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 npm1MIT