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