Developer overview
Pick the right way to connect your code to transglot: the CLI, the GitHub Action, the REST API, webhooks, the runtime SDKs, the in-context editor or the MCP server.
transglot keeps the strings of your app in a project. Everything on this page moves strings between that project and your code: up from your repository, back down as translated files, or straight into your running app.
The API lives at https://api.transglot.ai/v1. The app, where you manage projects and create credentials, is at https://app.transglot.ai. The CLI, the GitHub Action, the API, webhooks, the in-context editor, CDN delivery and the MCP server need the Starter plan or above; see pricing.
MCP server
Give an AI agent the tools to work on a project.
Command line tool
One command connects a repository; push and pull locale files from your terminal or any CI.
GitHub Action
Translate on every push and commit the finished files back to the branch.
REST API
Authentication, errors, rate limits and versioning for the public API.
API reference
Every endpoint, parameter and response.
Webhooks
Signed events when translations change, delivered to your endpoint.
Runtime SDKs
Load published translations in your app without a rebuild.
In-context editor
Let reviewers edit strings on your live site.
Editor plugins
Translations and missing keys in your editor, through the language server.
File formats
The 20 file formats transglot reads and writes.
Choose your integration
| You want to | Use |
|---|---|
| Connect a repository from your laptop and run the first translation | npx transglot@latest init |
| Translate on every merge in GitHub and commit the results | The GitHub Action |
| Do the same in GitLab CI, CircleCI or any other pipeline | The CLI in CI |
| Read or write translations, start runs or manage the glossary from your own code | The REST API |
| Start a build or notify a team when translations change | Webhooks |
| Ship translation fixes without releasing your app | The runtime SDKs and the CDN |
| Let reviewers fix wording on the real page | The in-context editor |
| Ask an AI assistant to fill gaps or check a key in every language | The MCP server |
| See missing translations while you edit message files | The language server |
| Check that your files are supported | File formats |
If nobody on your team writes code, you can still upload and download files in the app. See Do I need a developer to set transglot up?
Authentication
Each integration authenticates with one of three kinds of credential. All of them belong to a project and are created under Settings → Developer in that project.
| Credential | Used by | Keep secret? |
|---|---|---|
Deploy token (tgl_…) | The CLI, the GitHub Action, the REST API, the MCP server and the language server | Yes. Shown once, at creation. |
Publishable key (taip_…) | The in-context editor SDK in your app | No. Safe in client JavaScript, limited to the origins you allow. |
CDN key (taicdn_…) | Fetching published bundles from the CDN | Yes. Read-only, shown once. |
A deploy token carries abilities (push, pull, manage, read, write) that limit what it can do. Give each token only the abilities its job needs.