Lokalise MCP Tool
mdrafee03LABSCO SUMMARY
Per-project by design, key and all.
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.
What it is
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.
What you get
- 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
Requirements
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 (version 0.1.0).
Setup effort
Build from source — git clone https://github.com/GalvinGao/mcp-simplelocalize.git
USE CASES
01
Localizing a component as you write it
Ask for the strings to be extracted and pushed to SimpleLocalize in the same instruction that changes the component.
02
Keeping key naming consistent
Describe the namespace and naming style in the rules file so every new key matches the ones already there.
03
Working across several translation projects
Keep the configuration and its key inside each project rather than in a global client config, since the key is project-scoped.
BEFORE YOU INSTALL
What to know first
Requires
SIMPLELOCALIZE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/GalvinGao/mcp-simplelocalize.git
cd mcp-simplelocalize
uv syncMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"simplelocalize": {
"command": "uv",
"args": [
"run",
"--project",
"<YOUR_PATH_TO_MCP_SIMPLELOCALIZE>",
"<YOUR_PATH_TO_MCP_SIMPLELOCALIZE>/main.py"
],
"env": {
"SIMPLELOCALIZE_API_KEY": "<YOUR_SIMPLELOCALIZE_API_KEY>"
}
}
}
}
