Read, search, edit and branch Translatize translation labels and fill missing translations.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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. |
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).
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/mcp-149)<a href="https://allmcps.com/mcp/mcp-149"><img src="https://allmcps.com/api/badge/mcp-149?style=directory" alt="Translatize MCP on AllMCPs" /></a>