add_lokalise_keys
Add multiple translation keys to a Lokalise project using structured input
LABSCO SUMMARY
A write-only slice of Lokalise: it adds keys and does nothing else, which is either exactly the integration you wanted or not enough of one.
add_lokalise_keys is the entire surface — there is no read, no list and no update alongside it, so this fits a workflow where new strings are drafted in conversation and pushed straight across, and does not fit one where you need to see what is already in the project first. Addressing by projectName rather than an id keeps the call readable and puts the weight on that name being unambiguous in the account.
What it is
A one-call Lokalise writer: add_lokalise_keys takes a structured keys payload and a projectName, and adds those keys to that project.
What you get
- add_lokalise_keys adds translation keys in a batch rather than one at a time, taking them as structured input.
- The destination is addressed by projectName, so the call is written the way the project is spoken about.
Requirements
A Lokalise account with an API token, supplied as LOKALISE_API_KEY.
Setup effort
One command plus a key — npm install -g lokalise-mcp-server, then supply credentials
USE CASES
01
Getting newly written copy into translation without a dashboard trip
Hand over the keys as structured input and name the project they belong to; the batch goes across in one call.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected. The tool only writes: add_lokalise_keys pushes new keys into a Lokalise project and cannot list projects, read keys or pull translations.
Requires
- npx on PATH
- Node.js 22+
- LOKALISE_API_KEY in your environment
Where it runs
All 3 documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g lokalise-mcp-serverMCP Clients
Cursor — npx
CURSOR — NPX · JSON
{
"mcpServers": {
"lokalise": {
"command": "npx",
"args": [
"-y",
"lokalise-mcp-server"
],
"env": {
"LOKALISE_API_KEY": "<YOUR_LOKALISE_API_KEY>"
}
}
}
}Cursor — Docker
CURSOR — DOCKER · JSON
{
"mcpServers": {
"lokalise": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"LOKALISE_API_KEY",
"rafee03/mcp-lokalise:latest"
],
"env": {
"LOKALISE_API_KEY": "<YOUR_LOKALISE_API_KEY>"
}
}
}
}Cursor — local build
CURSOR — LOCAL BUILD · JSON
{
"mcpServers": {
"lokalise": {
"command": "node",
"args": [
"<YOUR_DIRECTORY_PROJECT>/dist/mcp-server.js"
],
"env": {
"LOKALISE_API_KEY": "<YOUR_LOKALISE_API_KEY>"
}
}
}
}
