Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read, edit, branch, translate and QA-check Translatize translation labels from AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TRANSLATIZE_API_TOKEN, TRANSLATIZE_API_URL, TRANSLATIZE_APP_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"translatize": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "your-value",
"TRANSLATIZE_API_URL": "your-value",
"TRANSLATIZE_APP_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add translatize --env TRANSLATIZE_API_TOKEN=your-value --env TRANSLATIZE_API_URL=your-value --env TRANSLATIZE_APP_URL=your-value -- npx -y @translatize/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"translatize": {
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "your-value",
"TRANSLATIZE_API_URL": "your-value",
"TRANSLATIZE_APP_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"translatize": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@translatize/mcp"
],
"env": {
"TRANSLATIZE_API_TOKEN": "your-value",
"TRANSLATIZE_API_URL": "your-value",
"TRANSLATIZE_APP_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
TRANSLATIZE_API_URL envTRANSLATIZE_APP_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain translatize.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TRANSLATIZE_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/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).
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. |
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, @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.