Allows AI agents to read, edit, branch, translate, and QA-check translation labels via the Translatize integration API.
Also known as Translatize/integrations, integrations, @translatize/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Nov 3, 2026
- License
- —
What is Translatize MCP?
Translatize allows AI agents to read, edit, branch, translate, and QA-check translation labels via the Translatize integration API.
Summary generated from the project's README
About Translatize MCP server
Managing localization workflows through AI agents is possible with this MCP server. It connects tools like Claude Code and Cursor to the Translatize integration API via stdio, allowing models to interact directly with your translation data. Developers use this to automate the reading, editing, and branching of translation labels without leaving their coding environment.
To use the server, you must provide a machine token for authentication using the Authorization: Bearer mcni_ format. The server provides 28 distinct tools and two workflow prompts to assist with internationalization tasks. It is built on the @translatize/core SDK and is designed to work within an npm workspace environment. This setup enables agents to perform complex QA-checks and manage translation strings through a standardized protocol.
What you can do with it
- 1Integrate with AI-powered IDEsConnect your translation API to Cursor or Claude Code to manage strings via natural language.
Written from the project's README. Every use case is checked against a quote from it.
How to install Translatize MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Translatize MCP in Claude Code
$ claude mcp add --env 'TRANSLATIZE_API_TOKEN=<YOUR_TRANSLATIZE_API_TOKEN>' integrations -- npx -y @translatize/mcpInstall Translatize MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"integrations": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<YOUR_TRANSLATIZE_API_TOKEN>"
}
}
}
}Install Translatize MCP in VS Code
.vscode/mcp.json
{
"servers": {
"integrations": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<YOUR_TRANSLATIZE_API_TOKEN>"
}
}
}
}Install Translatize MCP in VS Code CLI
$ code --add-mcp '{"name":"integrations","type":"stdio","command":"npx","args":["-y","@translatize/mcp"],"env":{"TRANSLATIZE_API_TOKEN":"<YOUR_TRANSLATIZE_API_TOKEN>"}}'Install Translatize MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"integrations": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<YOUR_TRANSLATIZE_API_TOKEN>"
}
}
}
}Install Translatize MCP in Codex
$ codex mcp add integrations --env 'TRANSLATIZE_API_TOKEN=<YOUR_TRANSLATIZE_API_TOKEN>' -- npx -y @translatize/mcpInstall Translatize MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.integrations] command = "npx" args = ["-y", "@translatize/mcp"] [mcp_servers.integrations.env] TRANSLATIZE_API_TOKEN = "<YOUR_TRANSLATIZE_API_TOKEN>"
Install Translatize MCP in Gemini CLI
$ gemini mcp add -s user -e 'TRANSLATIZE_API_TOKEN=<YOUR_TRANSLATIZE_API_TOKEN>' integrations npx -- -y @translatize/mcpInstall Translatize MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"integrations": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<YOUR_TRANSLATIZE_API_TOKEN>"
}
}
}
}Configuration
TRANSLATIZE_API_TOKENRequiredSecretTranslatize integration API token (an "mcni_..." string), bound to one project and branch. Create it under Project Settings -> Integrations at https://app.translatize.com.
TRANSLATIZE_API_URLAPI base URL including the /v1 segment. Defaults to https://api.translatize.com/v1.
TRANSLATIZE_APP_URLWeb-app base URL used to build review links. Defaults to https://app.translatize.com.
| Name | Description | |
|---|---|---|
| TRANSLATIZE_API_TOKEN | Translatize integration API token (an "mcni_..." string), bound to one project and branch. Create it under Project Settings -> Integrations at https://app.translatize.com. | RequiredSecret |
| TRANSLATIZE_API_URL | API base URL including the /v1 segment. Defaults to https://api.translatize.com/v1. | |
| TRANSLATIZE_APP_URL | Web-app base URL used to build review links. Defaults to https://app.translatize.com. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachabletranslatize/integrations is public and reachablegithub.com/translatize/integrations ↗Pass
- Package names this repository as its source@translatize/mcp names translatize/integrations as sourcenpmjs.com/package/@translatize/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-03github.com/translatize/integrations ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @translatize/mcpPass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubTranslatize integrations
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.
Packages
| 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/qa/screenshots upload/release) built on @translatize/core. Syncs translations from CI with git-like branching, gates on QA, uploads screenshot captures and publishes OTA releases. |
@translatize/mcp |
mcp/ |
available | Model Context Protocol server exposing the API to AI agents (Claude Code, Cursor, ...) over stdio, built on @translatize/core: 28 tools and 2 workflow prompts. |
@translatize/playwright |
playwright/ |
new in 0.2.0 | Captures screenshots with text positions from Playwright tests, for translatize screenshots upload. |
@translatize/ota |
ota/ |
new in 0.2.0 | Zero-dependency over-the-air client (browser, React Native, Node) with an i18next backend. |
@translatize/ota-worker |
ota-worker/ |
private | The Cloudflare Worker that serves OTA releases. Deployed with wrangler, not published. |
@translatize/github-app |
github-app/ |
private | The GitHub App service (container). Not published. |
The Claude Code plugin in claude-plugin/ bundles the MCP
server plus two skills (localize-repo, translatize-strings).
CI templates
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/qa for GitHub workflows. |
| GitLab CI | gitlab.com/translatize/gitlab | CI/CD Catalog component (templates/translatize.yml) plus copy-paste .gitlab-ci.yml jobs. |
Development
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).
Publishing
The @translatize/core, @translatize/cli, @translatize/mcp,
@translatize/ota and @translatize/playwright packages are published to npm
under the @translatize scope, in lockstep versions. Publishing is manual –
nothing here publishes automatically. Follow PUBLISHING.md:
build first, then npm publish --access public per package, core first. Don't use
npm publish --workspaces – it would also try the private packages.
Translatize MCP questions
How do I add Translatize MCP to Claude Code?
Run claude mcp add --env 'TRANSLATIZE_API_TOKEN=<YOUR_TRANSLATIZE_API_TOKEN>' integrations -- npx -y @translatize/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Translatize MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can AI agents do with this server?
AI agents can use the 28 tools and 2 workflow prompts provided to read, edit, branch, translate, and perform QA-checks on translation labels.
Which AI clients are compatible with this MCP server?
The server is designed to work with AI agents such as Claude Code and Cursor.
How is the Translatize integration API authenticated?
The API uses machine-token authentication via a Bearer token.