Because a SimpleLocalize key belongs to one project, the setup deliberately lives in the project rather than in a global client config — with a reminder to keep it out of version control. The other half of making this work is the rules file: state the namespace, the supported language codes and the key naming style there once, and the assistant stops inventing conventions on each component.
An MCP server for SimpleLocalize, the translation management platform. It connects a coding assistant to one SimpleLocalize project so extracting strings from a component and pushing them upstream happens in the same step as writing the component.
- A path from editor to translation project — "localize this component and update it to SimpleLocalize" becomes one instruction rather than a copy-paste round trip
- Project conventions the assistant will follow, if you describe them in the rules file: which namespace strings go in, which language codes the project supports, and your key naming style
A SimpleLocalize API key as `SIMPLELOCALIZE_API_KEY`. The key is specific to one project, so the README recommends putting the config in `.cursor/mcp.json` under the project root and adding it to `.gitignore` rather than configuring it globally. `uv` for dependencies: clone, run `uv sync`, and launch it with `uv`, passing `--project` for the checkout and `main.py` as the entry point. The package is `simplelocalize-mcp` (0.1.0 in pyproject).