WebTranslateIt MCP server
Commit Nov 12, 2026Lets an AI assistant manage translations, look up keys, check progress, and sync language files via the WebTranslateIt API.
Also known as FireZenk/wti-mcp
- Stars
- 0
- Tools
- 11
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 12, 2026
- License
- MIT
What is WebTranslateIt MCP?
WebTranslateIt lets an AI assistant manage translations, look up keys, check progress, and sync language files via the WebTranslateIt API. It exposes 11 tools, such as wti_get_project, wti_get_stats, wti_list_strings.
Summary generated from the project's README
About WebTranslateIt MCP server
Managing localization projects through an AI assistant is what this server enables for developers using WebTranslateIt. It provides a bridge between your AI client and the WebTranslateIt REST API, allowing you to handle translation tasks that typically require the command line interface or web dashboard. You can use it to look up specific keys, check translation progress across different locales, and manage your glossary terms directly from a chat interface.
The server runs locally and requires a Bearer token or a project API key provided via environment variables. It supports various modes, including a read-only setting to prevent accidental changes and an optional delete mode if the WTI_ALLOW_DELETE variable is enabled. Users can interact with tools like wti_get_stats to monitor completion percentages or wti_list_strings to search for specific keys using regex. It also handles file synchronization through wti_download_file and wti_upload_file, ensuring your local language files stay in sync with the remote project.
What you can do with it
- 1Identify untranslated contentAsk the assistant to find which keys in a specific language still need translations and draft new versions using the glossary.
- 2Monitor localization progressRequest a status report to see which locales are falling below a certain translation percentage.
- 3Bulk create and translate keysInstruct the AI to add a new string with specific labels and provide translations for multiple languages at once.
- 4Audit developer commentsSearch for specific keys that are missing documentation or comments for developers.
Written from the project's README. Every use case is checked against a quote from it.
WebTranslateIt MCP tools 11
Detected from the READMEwti_get_projectwti_get_statswti_list_stringswti_get_stringwti_download_filewti_search_glossarywti_create_stringwti_update_stringwti_set_translationswti_upload_filewti_add_locale
Configuration
WTI_CONFIG_FILE
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablefirezenk/wti-mcp is public and reachablegithub.com/firezenk/wti-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/firezenk/wti-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model11 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubwti-mcp
An MCP server for WebTranslateIt. It lets an
AI assistant look up keys and their translations, find what's left to translate, create and edit strings, save
translations, check progress, use the glossary, and push or pull language files — the things you'd otherwise do
with the wti CLI or the web UI.
It talks to the WebTranslateIt REST API the same way wti 3.x does: a Bearer token and
/api/projects/current (or /api/projects/<id> for organization tokens).
This is an independent project, not made or endorsed by WebTranslateIt.
What you can ask
- "Which keys are still untranslated in de-DE? Draft translations for them, matching the glossary."
- "Show me
booking_confirm_titlein every language." - "Add the key
rebook_card_titlewith the text 'Book again', label itrelease-5.31, and translate it into French and Spanish." - "How far along is each locale? Which ones are below 90% translated?"
- "Find every key starting with
checkout_that has no developer comment."
Tools
| Tool | What it does | Mode |
|---|---|---|
wti_get_project |
Source/target locales and master files with their ids | read |
wti_get_stats |
Progress per locale: done, to translate, to verify, to proofread, % done and % translated | read |
wti_list_strings |
List or search strings by key (exact or regex), label, file, status, date; with translations | read |
wti_get_string |
One string by key or id, with its translation in every locale | read |
wti_download_file |
Download a language file for a locale (one-file wti pull) |
read |
wti_search_glossary |
Search the term base, optionally with translations in a locale | read |
wti_create_string |
Create a key with its source text, translations, comment and labels | write |
wti_update_string |
Rename a key, change its comment, labels (add/remove) or status | write |
wti_set_translations |
Save a string's translation in one or more locales | write |
wti_upload_file |
Compare a local language file with WebTranslateIt's copy, then upload it (one-file wti push) |
write |
wti_add_locale |
Add a target locale | write |
wti_create_term, wti_update_term, wti_set_term_translation |
Edit the glossary | write |
wti_delete_string, wti_delete_term, wti_remove_locale |
Delete things | delete |
Write tools aren't registered in read-only mode. Delete tools are only registered with WTI_ALLOW_DELETE=true.
Setup
Requires Node.js 22 or newer.
git clone https://github.com/FireZenk/wti-mcp.git
cd wti-mcp
npm install # also builds dist/
The server is then node /path/to/wti-mcp/dist/index.js.
Configuration
| Variable | Meaning |
|---|---|
WTI_API_TOKEN |
API token (wti_pw_…, wti_iw_…, …) or legacy project API key. |
WTI_PROJECT_API_KEY |
Same, under the name the wti gem uses. |
WTI_CONFIG_FILE |
Path to a .wti file to read api_key and project_id from, so an existing wti setup works as is. <%= ENV['NAME'] %> is expanded. |
WTI_PROJECT_ID |
Numeric project id. Needed for organization tokens only. |
WTI_READ_ONLY |
true to expose read tools only. Automatic for read-only tokens (wti_pr_…, wti_ir_…). |
WTI_ALLOW_DELETE |
true to also expose the delete tools. |
WTI_BASE_URL |
Defaults to https://webtranslateit.com. Must be https (localhost excepted, for testing). |
Environment variables win over the .wti file.
Claude Code
Reusing the .wti of a project:
claude mcp add wti -e WTI_CONFIG_FILE=/path/to/your/app/.wti -- node /path/to/wti-mcp/dist/index.js
Or with a token:
claude mcp add wti -e WTI_API_TOKEN=wti_pw_… -- node /path/to/wti-mcp/dist/index.js
Add -e WTI_READ_ONLY=true for a read-only setup. Each server instance works on one project: add one per project
(e.g. wti-android, wti-ios) if you have several.
Claude Desktop and other MCP clients
{
"mcpServers": {
"wti": {
"command": "node",
"args": ["/path/to/wti-mcp/dist/index.js"],
"env": { "WTI_CONFIG_FILE": "/path/to/your/app/.wti" }
}
}
}
Things worth knowing
- Locale codes are the project's own:
de-DE, notde, if that's how the project is set up. Tools check the code against the project and suggest the right one. - Keys are unique per file.
wti_get_stringand friends accept a key and find its id; passfile_idwhen the same key exists in several files. The API's key filter matches prefixes, so the server picks the exact match. - Writes are asynchronous. WebTranslateIt answers 202 Accepted and applies changes in the background; re-read after a few seconds before relying on them.
wti_upload_filechecks WebTranslateIt before uploading. Neitherwti pushnor the API looks at what changed on WebTranslateIt since your last pull. Called withoutconfirm, the tool uploads nothing: it downloads the current copy and lists the lines that are only there (someone else's changes, which the upload could overwrite) and the lines only in your file. The upload happens on a second call with theconfirmtoken from that preview. The token is tied to both files' content, so if either changes in between you get a new preview instead of an upload. The comparison ignores line order, indentation and blank lines; it works best on files that came from awti pull, since WebTranslateIt's export formatting may differ from a hand-written file.wti_upload_filekeeps missing strings by default (ignore_missing: true), unlike the API, so uploading a partial file can't mark the rest of the project obsolete. Passignore_missing: falseto sync deletions. Withmerge: false(the default) your file's text replaces WebTranslateIt's where they differ; withmerge: trueWebTranslateIt keeps its text and only adds what it doesn't have.- Statuses. Translations:
status_unproofread,status_proofread,status_unverified. Strings:current,hidden,obsolete. In stats,doneonly counts proofread strings;percent_translatedalso counts the ones waiting for proofreading. - Glossary translation statuses can only be set on creation. WebTranslateIt's API answers 500 to a status
name on update and silently ignores a numeric one, so
wti_set_term_translationonly updates the text and description of an existing translation and says so. Statuses read back as numbers (1, 0, -1); the server shows them asapproved,proposed,refused. - WebTranslateIt doesn't reject a translation that drops a placeholder (e.g.
%1$s) when saved through the API, so check placeholders yourself. - Rate limits. The API allows 25 requests per second per IP. The client retries 429 responses (honouring
Retry-After) and, for GET requests only, timeouts and 502/504. - The token only goes to the WebTranslateIt host. Pagination links pointing elsewhere are refused.
Development
npm test # unit and MCP-level tests against a fake WebTranslateIt
npm run typecheck
npm run inspect # open the server in the MCP Inspector (needs a token in the environment)
The code: src/client.ts (HTTP client), src/config.ts (environment and .wti), src/format.ts (compact
responses for the model), src/tools/* (tool definitions), src/server.ts and src/index.ts (stdio entry
point). See CONTRIBUTING.md.
Security
The server runs locally and only talks to WebTranslateIt with the token you give it. Texts coming back from
WebTranslateIt (translations, comments, glossary entries) are written by people and reach the model as data;
keep write access for setups where you review what the assistant does, and use WTI_READ_ONLY=true otherwise.
To report a vulnerability, use GitHub's "Report a vulnerability" in the Security tab rather than a public issue.
License
WebTranslateIt MCP questions
What tools does WebTranslateIt MCP provide?
It exposes 11 tools, including wti_get_project, wti_get_stats, wti_list_strings, wti_get_string, wti_download_file.
Can I use this server in read-only mode?
Yes, you can set the WTI_READ_ONLY environment variable to true to expose only read tools, or use a read-only token.
How does the server handle file uploads?
The wti_upload_file tool compares your local file with the WebTranslateIt copy first; it requires a confirmation token from a preview to perform the actual upload.
Are writes to the API instantaneous?
No, writes are asynchronous. WebTranslateIt accepts the request and applies changes in the background, so you should re-read after a few seconds.
Does the server support deleting strings or terms?
Yes, but you must explicitly enable this by setting the WTI_ALLOW_DELETE environment variable to true.