Babelize

Start here to make a React, Next.js or Django app global-ready (Vue, React Native/Expo and static HTML are beta). Scans the local project with the Babelize engine in dry-run mode on a temp copy: nothing is written, no network, no API key. Reports: framework and support level; whether the i18n library (next-intl / react-i18next / vue-i18n) is installed and wired up; hardcoded user-facing strings (count + file:line); JSX sentences kept whole as one ICU message vs split into pieces; strings that cannot be wired automatically and why; hardcoded dates/currencies/plurals; existing locale files and their coverage per locale; source keys that look unused (advisory); and next steps. Loop: babelize_analyze → babelize_translate → babelize_check (or babelize_review on a diff) → fix → repeat. Returns a short summary plus compact JSON; lists are capped by `limit`. Paths are relative to the project root.

Make the app global-ready: extract hardcoded strings, wire them to the i18n library (adding config/provider and package.json deps when missing), and translate every key into the target locales, writing locale files and code into the working tree. Same engine and result as `npx babelize translate`. Run babelize_analyze first; afterwards review `git diff` and run babelize_check. Requires a git repo with a clean working tree (commit or stash first; force: true overrides; dryRun: true previews without writing and works on a dirty tree). Incremental: a lockfile (.babelize/local/babelize-lock.json) means reruns only translate new or changed strings, and failed strings are retried on the next run. Earlier locales are kept and updated unless replace: true. Translation keys come from the MCP server environment, never from arguments: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, GROQ_API_KEY or OPENROUTER_API_KEY (your own LLM key), or a Babelize API key for Babelize-hosted translation (free tier): --api-key on this server, BABELIZE_API_KEY, or apiKey in .babelize/config.json. Returns files changed, per-locale translated/failed counts, failures with reasons, QA warnings, strings not wired into code, a diff summary (and a diff preview on dryRun). Sends progress notifications.

QA of the existing locale files against the source locale, without translating: no network, no API key, read-only. Use after babelize_translate or after editing locale files, and before committing. Finds: missing and stale keys; empty values; values identical to the source (untranslated); placeholders/tags lost or invented ({name}, {{count}}, <0>, %s); invalid ICU messages and wrong plural categories for the locale (ICU and i18next _one/_other keys); glossary violations (glossary in .babelize/config.json). Looks for <locale>.json (or <locale>/<namespace>.json) under locales/, messages/, lang/, i18n/ or translations/ folders. Returns per-locale counts and a capped list of issues (errors first) with file, locale, key and the problem in plain words.

Review the locale changes in the current git diff (working tree vs HEAD, including untracked files) or vs a base ref, e.g. before committing or in a PR. QAs only the changed entries with the same checks as babelize_check (missing keys, placeholders, ICU, plural forms, untranslated, glossary from .babelize/config.json), and flags source strings whose translations were not updated (stale) and new source keys a locale is missing. Read-only; no network, no API key.

Low-level: list hardcoded strings in a local directory (regex/AST scan, no framework detection). No API key required. For a whole-project localization report use babelize_analyze.

Low-level: extract hardcoded translatable strings from a code snippet. No API key required.

Cloud project management: List all translation projects. Requires BABELIZE_API_KEY.

Cloud project management: Get details of a specific translation project. Requires BABELIZE_API_KEY.

Cloud project management: Create a new translation project from a GitHub repository (repo_url is required). ZIP projects cannot be created here: their archive must be uploaded first, via the dashboard (Upload ZIP) or `babelize init --source zip`. Requires BABELIZE_API_KEY.

Cloud project management: List translation runs (babels). Requires BABELIZE_API_KEY.

Cloud project management: Get detailed info and logs for a translation run. Requires BABELIZE_API_KEY.

Cloud project management: List all supported languages. Requires BABELIZE_API_KEY.

無需輸入參數。

Cloud project management: Look up language code mappings (ISO ↔ FLORES-200). Requires BABELIZE_API_KEY.

Cloud project management: Analyze source code for framework detection and i18n readiness. Requires BABELIZE_API_KEY.

Cloud project management: List translation memory entries for a project. Requires BABELIZE_API_KEY.

Cloud project management: Add a translation memory entry. Requires BABELIZE_API_KEY.

Cloud project management: Export translation memory as TMX. Requires BABELIZE_API_KEY.

Cloud project management: Delete a glossary entry. Requires BABELIZE_API_KEY.

Cloud project management: Bulk import glossary entries from a CSV string (term,type,<locale>,…). Existing terms (matched ignoring case) are updated unless skip_existing is set. Reports added/updated/skipped/rejected rows. Requires BABELIZE_API_KEY.

Cloud project management: Export glossary entries as CSV. Requires BABELIZE_API_KEY.

Cloud project management: Add a language to a project. Requires BABELIZE_API_KEY.

Cloud project management: Remove a language from a project. Requires BABELIZE_API_KEY.

Cloud project management: List members of a project. Requires BABELIZE_API_KEY.

Cloud project management: Send a team invitation to a project. Requires BABELIZE_API_KEY.

Cloud project management: Trigger a repository sync for a project. Requires BABELIZE_API_KEY.

Cloud project management: Create a GitHub Pull Request with the latest run's translations. If the project's PR is still open (same target languages), the run is added to it instead. Requires BABELIZE_API_KEY.

Cloud project management: Push the latest run's translations to the project's open GitHub Pull Request. Requires BABELIZE_API_KEY.

Cloud project management: Download translated project files as ZIP. Requires BABELIZE_API_KEY.

Cloud project management: Get current user profile and credits. Requires BABELIZE_API_KEY.

無需輸入參數。

Cloud project management: List connected BYOK translation provider tokens. Requires BABELIZE_API_KEY.

無需輸入參數。

Cloud project management: Trigger a Babelize translation run for target languages. Requires BABELIZE_API_KEY.

Cloud project management: Start a translation run and poll until it completes. Requires BABELIZE_API_KEY.

Cloud project management: Check status of a translation run. Requires BABELIZE_API_KEY.

Cloud project management: List glossary entries for a project, with each entry's id (for babelize_glossary_delete) and the total count. Paged: 100 entries per page by default. Requires BABELIZE_API_KEY.

Cloud project management: Add or update a glossary entry. never_translate keeps the term as written in every language (no target needed). always_translate_as sets the required translation of the term for one locale; calling it again for another locale adds that locale to the same entry. An existing entry for the term (matched ignoring case) is updated, not duplicated. Requires BABELIZE_API_KEY.