Translatize runs on your own machine — the client starts it, so there is no endpoint to ping. 94 installs a week from npm. Last commit 3 Nov 2026.
Read, edit, branch, translate and QA-check Translatize translation labels from AI agents.
Today is the operative word: we check Translatize every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -e 'TRANSLATIZE_API_TOKEN=<TRANSLATIZE_API_TOKEN>' -- npx -y @translatize/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<TRANSLATIZE_API_TOKEN>"
}
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@translatize/mcp"]
env = { TRANSLATIZE_API_TOKEN = "<TRANSLATIZE_API_TOKEN>" }
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<TRANSLATIZE_API_TOKEN>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "<TRANSLATIZE_API_TOKEN>"
}
}
}
}
Put your own value in place of
<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).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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).
Translation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing.
Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate.
Public web tools for agents: product extraction, claim checks, webpage QA and ranked audits.
Local browser automation for AI agents: real-browser fetch, capture, smoke tests, cross-engine QA.
Local browser automation for AI agents: real-browser fetch, capture, smoke tests, cross-engine QA.
Create, launch, and analyze user research studies, AI interviews, and AI tests from your AI agent.
A/B testing for vibe coders: create, track, and ship experiments from your AI coding agent.
Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.
Answers built from our own checks of this server.