Skip to content
Agentmart
Submit a tool

Translatize

Read, search, edit and branch Translatize translation labels and fill missing translations.

Connector by translatize.com · Domain verified by the MCP Registry

IndexedLicense unknownLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/translatize-com-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Read, search, edit and branch Translatize translation labels and fill missing translations.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
11 read · 5 write · 1 delete · 1 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 18

Read from the source code; the running server may list different tools.

Read 11 · Look things up without changing anything.

  • compare_with_base
  • get_labels
  • get_merge_conflicts
  • get_missing_translations
  • get_project_info
  • list_branches
  • list_labels
  • review_changes
  • search_labels
  • translation_job_status
  • translation_status

Write 5 · Create, change, send or run things.

  • create_branch
  • merge_branch
  • set_labels_status
  • upsert_label
  • upsert_labels

Delete 1 · Delete, drop, revoke or wipe things.

  • delete_branch

Not yet classified 1 · We could not tell from the name and description.

  • auto_translate

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • TRANSLATIZE_API_TOKEN

Other settings (environment variables or headers).

  • TRANSLATIZE_API_URL
  • TRANSLATIZE_APP_URL

Tools (18)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • auto_translate

    Trigger Translatize's PLATFORM AI to fill in missing translations on a branch as a background job. It is available only on plans that include it (professional/agency), and it is metered against the AI quota. Optionally scope to specific target_languages (defaults to every project language except the source), specific label_keys, and set overwrite_translated to re-translate values that already exist. Returns the started job (poll it with translation_job_status) or a no-op when nothing needs translating. If it fails with feature_not_available, the plan has no platform AI; fall back to get_missin…

  • compare_with_base

    Compare a branch (the source) against the token's base branch (the target): returns the changed, added and deleted keys, each with the differing per-language source/target values, plus a summary of counts. The branch must be in the token's allowed set. Use this to see exactly what a branch would bring into the base before merging. For a capped, human-oriented review view, use review_changes instead.

  • create_branch

    Create a new branch, forked from the token's base branch (you cannot choose a different base), then work on it by passing its name as `branch` to the label tools. Requires a create-own scoped token and the developer role or higher. A fixed-scope token fails with branch_scope_fixed; when that happens, tell the user to issue a create-own token under Project Settings -> Integrations. Name rules: 1-100 characters matching ^[a-zA-Z0-9_-]+$, and not "main". Returns the created branch. This is the typical first step of a change: create a branch, edit/translate on it, review_changes, then merge_branch…

  • delete_branch

    Delete a branch this token created (createdByThisToken=true in list_branches). Requires the developer role or higher. The base branch and any branch the token did not create can never be deleted; deleting them fails with not_token_branch. Use this to clean up after a successful merge_branch.

  • get_labels

    Fetch the full record (all per-language values, status and tags) for a specific set of label keys on a branch. Use this when you already know the exact keys you need, for example from list_labels or search_labels, and want their complete translations. Returns the found labels plus a not_found list of any requested keys that do not exist on the branch. Reads the token's base branch unless `branch` names another allowed branch.

  • get_merge_conflicts

    List the per-key, per-language merge conflicts between a branch (source) and the token's base branch (target): the cases where both sides hold a different non-empty value. Returns a flat conflicts array plus hasConflicts / conflictCount. An empty list means the branch is safe to merge with the default (overwrite) strategy. When there ARE conflicts and you want to resolve each one explicitly, use this first, then pass the resolutions to merge_branch with strategy "manual". The branch must be in the token's allowed set.

  • get_missing_translations

    Description is built at runtime.

  • get_project_info

    Get an overview of the Translatize project this server is connected to: its name and id, the configured languages, the base branch the API token is bound to, the token's role, the branch scope (fixed = only the base branch is writable; create-own = the token may also create and manage its own branches), the names of the branches this token may write to, the total number of label (translation-key) records, and per-language completeness percentages. Use this first to learn which project, branch, languages and scope you are working with. Takes no arguments.

  • list_branches

    List every branch in the project, each flagged with writable (whether this token may read/write/export it) and createdByThisToken (whether this token created it). Also returns baseBranch (the branch the token is bound to) and branchScope (fixed = only the base branch is writable; create-own = the token may additionally create branches and manage the ones it creates). Use this to see which branches exist and which you are allowed to act on before compare/merge/delete. Takes no arguments.

  • list_labels

    Description is built at runtime.

  • merge_branch

    Merge a branch this token created back into the token's base branch (the implicit, only-allowed target). Requires a create-own token with the developer role or higher. The merge does NOT delete the source branch. Call delete_branch afterwards to clean it up. Strategies: overwrite (default; a non-destructive union where the source wins conflicts and keys only on the base are kept), keep-newer (whichever side changed more recently wins), manual (you supply per-conflict resolutions obtained from get_merge_conflicts), and replace (DESTRUCTIVE: the base becomes an exact copy of the source; use only…

  • review_changes

    Description is built at runtime.

  • search_labels

    Description is built at runtime.

  • set_labels_status

    Set the workflow status of many labels at once (draft, review, approved or rejected) WITHOUT changing their translation values. Pass the keys and the target status. Use this to mark keys as reviewed or approved as part of a review workflow. Returns the updated/created counts and any per-key failures. Writes to the token's base branch unless `branch` names another allowed branch.

  • translation_job_status

    Report the project's current or most-recent AI translation job: its status (queued/running/completed/failed), target languages, progress counts, and (while queued) its position in the global queue. Also returns the AI quota (used / limit / remaining; a limit of -1 means unlimited). Use this to watch a job started by auto_translate, or to check the remaining quota before starting one. Takes no arguments.

Show 3 more tools
  • translation_status

    Description is built at runtime.

  • upsert_label

    Create or update a single label on a branch (upsert by key). Provide the key plus any of values (an object of languageCode -> string), status, or tags. Every language in values must be configured on the project, or the call is rejected with unknown_languages. Returns whether the label was created or updated and its resulting stored state. Use this to add a new translation key or change an existing one. Writes to the token's base branch unless `branch` names another allowed branch.

  • upsert_labels

    Create or update many labels on a branch in one call (batched automatically, with no client-side size limit). Pass labels as an array of { key, values?, status?, tags? }. Returns counts of created and updated labels plus a failed list of any individual items the server rejected (for example, an unknown language on one item). Use this instead of repeated upsert_label calls when writing more than a couple of keys. Writes to the token's base branch unless `branch` names another allowed branch.

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Oct 23, 2026 (5 days ago)
Last release
Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
com.translatize/mcp
Version
0.1.3
Auth
API key
Packages
npm @translatize/mcp
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Translatize MCP server. Agent Mart. https://agentmart.dev/connectors/translatize-com-mcp (last updated 2026-10-24)