Translation Sync MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSLATION_SYNC_ROOT | No | Overrides the project root used by the server. If unset, the server resolves the nearest enclosing git repository root, then falls back to two directories above the script. | |
| TRANSLATION_SYNC_I18N_PATH | No | Path to the locale folder, relative to the project root. Defaults to src/assets/i18n. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_translationsB | Synchronize translation keys from English source file to all target language files using MyMemory API (free, no API key required). Also removes keys that no longer exist in the source. |
| preview_changesA | Preview what translation keys have been added, modified, or deleted in the source file relative to the last sync (cache-based) |
| preview_git_changesA | Preview translation keys added, modified, or deleted between a git ref and the current working tree (JSON-diff based, not text-diff based — immune to comma-shift false positives) |
| list_available_languagesA | List language codes and names. "project" scope (default) lists the locale folders this project actually has under its i18n path; "all" scope lists every language MyMemory's free API can translate to, regardless of whether this project has a locale file for it. |
| translate_textB | Translate a specific text to a target language using MyMemory API (free, no API key required) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: sync performs writes, two previews use different comparison baselines (cache vs git ref), list reports locales, and translate_text handles ad hoc translation. The most similar pair, preview_changes and preview_git_changes, is explicitly differentiated by baseline and description.
All tool names use snake_case with a verb-first pattern: sync_translations, preview_changes, preview_git_changes, list_available_languages, translate_text. The convention is predictable and readable throughout.
Five tools is well-scoped for a translation synchronization server. Each tool supports a distinct part of the workflow without obvious bloat or missing core operations.
The tool set covers the core lifecycle: syncing translations, previewing changes from cache and git, listing languages, and translating individual text. Minor gaps exist around cache/config management or per-key editing, but agents can work around them.