$ loading_
Lets AI directly read and update locale JSON translation files.
This MCP tool is described as directly reading and writing local locale JSON translation files from conversations, with no required secrets and no declared remote endpoints, so its overall risk is low to moderate. The main concerns are its local code-execution and file-write capabilities, while the open-source source has weak adoption and unclear maintenance.
The material explicitly states that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication requirements are described, so credential exposure and misuse risk appears low.
No remote endpoints or external service connections are declared in the material. There is no stated evidence that conversation content or file data is exfiltrated to third parties, so network egress risk appears low based on the available facts.
The system checks indicate that it executes code and runs as an MCP service, meaning it processes requests in a local process. This local execution capability is normal for such tools, but it still warrants caution because it can be used to modify translation files or handle unexpected inputs.
The description explicitly states that the tool can directly read and write locale JSON translation files, so it clearly has local file read/write access. The material does not specify directory restrictions, file-type limits, or path validation, so attention should be paid to whether it could access files beyond the intended translation directory.
A positive factor is that there is an auditable open-source repository. However, the source is a third-party registry, the license is undeclared, community adoption is 0 stars, and maintenance status is unknown, so trust and ongoing maintenance signals are weak and the source code and dependencies should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-locator" yet — see the docs or source repo.
Check the zh-CN and en-US locale JSON files, find missing English keys, and fill them with natural, concise product UI copy while keeping the keys unchanged.
The tool directly updates the target locale file with the missing English translations.
Scan the current translation files, standardize all terms related to “workspace,” list the keys you changed with reasons, and write the updates back to the JSON files.
You get updated translation files with standardized terminology and a summary of the changes made.
Rewrite the Chinese and English translations for the settings page in a friendlier, more concise tone, avoid harsh command-style wording, and save changes only to the relevant existing keys.
The tool updates the bilingual copy, preserves the original structure, and writes it directly into the translation JSON files.
Let AI manage app translation files efficiently without loading whole locale files.
Provides localization data for 174 locales to create culturally adapted multilingual content.
Let AI read, write, search files, and run local commands.
Manage local semantic dataspaces, ingest documents, and run semantic search via MCP.
Automatically translates Portuguese and English conversations to reduce LLM interaction costs.
Search official library docs and return clean text ready for LLM use.