MCP.Market

Translatize MCP server

by translatize.com·com.translatize/mcp·v0.2.0
No reviews yet

Read, edit, branch, translate and QA-check Translatize translation labels from AI agents.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

0 stars22 downloads/wk

Reviews

Write one

Nobody has reviewed Translatize yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Translatize tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Translatize compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Downloads a week
22
more than 8% of 12,191 servers with a package

Release history: 3 versions in the registry since 2026-07-21, latest 2026-11-03, typically one every 94 days.

Install Translatize in Claude Code, Cursor or VS Code

Runs npx -y @translatize/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @translatize/mcp
Add to Cursor

What the publisher says

From the Translatize repository's README, as published. We do not edit it. Read it on GitHub

Translatize 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

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:

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, 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).

Nothing above is checked by us. What we check is on the safety report.

Translatize: common questions

Is Translatize MCP server safe?
Mostly: it is graded B (77/100). Read the Translatize safety report
How do I install Translatize?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Translatize need an API key?
Yes. The registry entry asks for TRANSLATIZE_API_TOKEN.
Is Translatize maintained?
The last commit was 106 days ago (2026-07-21). The latest release is v0.2.0.
How does Translatize compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); downloads a week 22 (more than 8% of 12,191 servers with a package). Full comparison.