Read, search, edit and branch Translatize translation labels and fill missing translations.
Client-side tooling for the Translatize integration API (the machine-token API
authenticated with Authorization: Bearer mcni_...). This is an npm workspace root
that is intentionally separate from the apps in the repo – it has the only
package.json with workspaces, and the repo root stays package.json-free.
| Package | Directory | Status | What it is |
|---|---|---|---|
@translatize/core | core/ | available | Zero-dependency TypeScript SDK for the integration API (client + flatten/unflatten helpers). The shared foundation everything else builds on. |
@translatize/cli | cli/ | available | Command-line tool (translatize init/pull/push/status) built on @translatize/core. Syncs translations from CI with git-like branching. |
@translatize/mcp | mcp/ | available | Model Context Protocol server exposing the API to AI agents (Claude Code, Cursor, ...) over stdio, built on @translatize/core. |
Two ready-to-use CI integrations complement the packages. They shell out to the
@translatize/cli (npx @translatize/cli ...) rather than being npm packages,
so you consume them as workflow/pipeline config, not via npm install:
| Template | Home | What it is |
|---|---|---|
| GitHub Action | github.com/Translatize/sync-action | Composite action (translatize/sync-action) wrapping the CLI's pull/push/status for GitHub workflows. |
| GitLab CI | gitlab.com/translatize/gitlab | CI/CD Catalog component (templates/translatize.yml) plus copy-paste .gitlab-ci.yml jobs. |
cd integrations
npm install # installs every workspace and hoists dev deps
npm run build # builds each workspace that defines a build script
npm test # runs each workspace's test suite
Requires Node.js >= 18.17 (native fetch, node:test).
The @translatize/core, @translatize/cli, and @translatize/mcp packages are
published to npm under the @translatize scope. Publishing is manual –
nothing here publishes automatically. To cut a release, build first, then
npm publish --access public from the individual package directory (or
npm publish --workspaces).
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @translatize/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-translatize-mcp": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@translatize/mcpnpmcom.translatize/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.