M
Mcp
Read, search, edit and branch Translatize translation labels and fill missing translations.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Install Config Generator
Choose your client
💡 Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Documentation Overview
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
| 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. |
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 for GitHub workflows. |
| GitLab CI | gitlab.com/translatize/gitlab | CI/CD Catalog component (templates/translatize.yml) plus copy-paste .gitlab-ci.yml jobs. |
Development
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).
Related MCP Servers
Frequently Asked Questions about Mcp
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-149)HTML Embed
<a href="https://allmcps.com/mcp/mcp-149"><img src="https://allmcps.com/api/badge/mcp-149?style=directory" alt="Mcp on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
27Quality signal: Emerging · 27/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to get the verified badge and attach your website.
Free dofollow backlink: after claiming, verify your product site and place a dofollow AllMCPs badge — we recheck it stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.