What can you do with the Lokalise integration?

LiveContext exposes 14 operations on Lokalise, covering key, project, file and language. Common uses include View project team, Submit translations and Export for app build.

LiveContext

All integrations

Lokalise integration

Translation and localization management platform for software teams. Manage translation keys, import/export translations, collaborate with translators, and automate localization workflows for apps, websites, and documents.

14 toolsAPI keyAPI docs

Connect Lokalise How integrations work

Common Lokalise use cases

View project team
Submit translations
Export for app build
Get project languages
Add new market language
Export translation keys
Rename translation keys
Add new strings from code
Get project configuration
Remove deprecated strings

What you can do with Lokalise

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Key, 4 operations

POSTcreate_keys
Creates new translation keys with optional initial translations.
DELETEdelete_keys
Deletes translation keys and all their translations.
GETlist_keys
Retrieves translation keys with optional translations, comments, and screenshots.
PUTupdate_key
Updates a translation key's name, description, or metadata.

Project, 3 operations

POSTcreate_project
Creates a new localization project with specified languages.
GETget_project
Retrieves detailed information about a specific localization project.
GETlist_projects
Retrieves all localization projects with optional translation statistics.

File, 2 operations

POSTdownload_files
Exports translation files in various formats (JSON, XLIFF, iOS, Android, etc.).
POSTupload_file
Imports a translation file to add or update keys and translations.

Language, 2 operations

POSTadd_languages
Adds new target languages to a project.
GETlist_languages
Retrieves all languages configured in a project.

Translation, 2 operations

GETlist_translations
Retrieves all translations with optional filtering by language or status.
PUTupdate_translation
Updates a translation's text and review status.

Contributor, 1 operation

GETlist_contributors
Retrieves all contributors (translators, reviewers) in a project.

Use Lokalise from Claude Code, Cursor or Codex

Connect Lokalise in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Lokalise operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Lokalise

Create your workspace
Sign up free. Nothing to install.
Connect Lokalise once
Add your Lokalise connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Lokalise integration FAQ

What can you do with the Lokalise integration?: LiveContext exposes 14 operations on Lokalise, covering key, project, file and language. Common uses include View project team, Submit translations and Export for app build.