Localization that fits
your git workflow

Yes, both are first-party. The zero-dependency transglot npm CLI gives you init, pull, push, and status (run it with npx transglot). The transglot GitHub Action pushes source files, waits for the AI batch, and pulls translations back — committing them to a branch or uploading them as an artifact. Both authenticate with a tgl_ project token, and the REST API remains available for anything custom.

Yes — that is what the @transglot/mcp server is for. It is a first-party Model Context Protocol server exposing 15 tools mapped 1:1 onto the public REST API: read a project and its languages, read and upsert translations, trigger and poll AI batches, retry failed ones, run QA, manage glossary terms, and pull or push whole files. Read-only tools are annotated as such; every mutating tool states exactly what it changes; and the three that consume AI word quota (translate_missing, retry_failed_batch, run_qa) declare that in their description so the agent can decide before it spends. Tools respect the same push / pull / manage token abilities as the API, so an agent never gets more access than the token you hand it.

Each project can generate scoped access tokens (tgl_ prefix, sha256-stored, revealed once) with push, pull, or manage abilities and an optional expiry. Requests are Bearer-authenticated and rate-limited. The CLI, the GitHub Action, and the MCP server all use the same tokens.

Register a per-project endpoint URL and it receives HMAC-SHA256-signed POST requests across 10 events: batch.completed, batch.failed, key.created, key.updated, key.deleted, translation.updated, translation.reviewed, language.added, glossary.updated, and qa.completed. Signatures let you verify authenticity before acting, high-frequency events are coalesced rather than firing once per row, a delivery log keeps the last 50 attempts, and any past payload can be manually redelivered.

Twenty formats: JSON (flat and nested), Android XML, iOS .strings, .stringsdict and .xcstrings, Flutter ARB, Laravel PHP/JSON, XLIFF 1.2 and 2.0, gettext .po, Rails-style YAML, Java .properties, .NET .resx, CSV and XLSX spreadsheets, Markdown/MDX documents, Unity Localization CSV, and Unreal Engine PO — covering i18next, React, Vue, Laravel, iOS, Android, Flutter, Rails, Java/Spring/Kotlin, .NET, and gettext projects today, plus any XLIFF-speaking CAT or TMS tool.

Yes. Publish your reviewed strings to the OTA/CDN endpoint — public, edge-cacheable, versioned, with ETag/304 revalidation — and read them at runtime with the zero-dependency @transglot/runtime SDK or its Vue, React, Svelte, Next.js, SvelteKit, Angular, and Solid adapters. A production string fix becomes a publish, not a build. Runtime delivery is included on every paid plan.

Yes. A per-project glossary (Indie and up) validates terminology deterministically after every translation — a forbidden term is always a hard failure. Translation QA (Team and up) adds a free placeholder-integrity and plural-completeness pre-gate plus an AI quality score, so you can gate a merge on real signal instead of eyeballing a diff.