Build with Translatize
Translation management with git-like branching. Sync translations straight from your codebase, gate them in CI, and let AI agents manage localization – all through one token-authenticated API.
Pull, push, and status-check translations from your terminal or CI with the translatize command.
Sync in GitHub workflows – push keys on merge, open PRs with fresh translations, or gate pull requests.
A CI/CD Catalog component and copy-paste jobs that run the CLI inside your GitLab pipelines.
Let AI agents like Claude Code and Cursor manage your translations over the Model Context Protocol.
The token-authenticated REST API every tool is built on – labels, exports, branches, and AI translation.
How it fits together
Everything speaks to the same integration API. The CLI is the workhorse; CI runs the CLI; AI agents reach the identical endpoints through the MCP server.
@translatize scope: @translatize/cli, @translatize/core, and @translatize/mcp. Install them with your package manager, or run the CLI directly with npx @translatize/cli@latest.Where tokens come from
Every tool authenticates with an API token – a string that begins with mcni_, not your login. Create one in the app under Project Settings → Integrations. A token is bound to a single project and a base branch.
For AI-agent workflows, mint a token with the create-own scope: it works only on its base branch and the branches it creates – it can never reach any other branch in the project. That limited blast radius is what makes it safe to hand an agent a token of its own.