Lokalise
Lokalise is a translation and localization management platform for managing multilingual content, projects, contributors, files, keys, translations, and localization workflows.
Integration
- Vendor
- Lokalise
- Category
- productivity
- Auth
- API_KEY
- Tools
- 10
- Composio slug
lokalise
Tools
- Create Keys
Create 1 to 500 keys in a Lokalise project or branch. Requires a personal read/write API token and the project's Manage keys admin right. Branch targets also require a compatible Software project with Branching enabled. The response retains
- Delete Keysdestructive
Permanently delete one or more keys from a Lokalise project or branch. This operation is irreversible and requires a personal read/write API token with key-management permission. Branch targets additionally require a compatible Software pro
- List Audit Logs
List one page of team audit events in OCSF 1.3.0 format. This endpoint requires a personal API token belonging to a team admin and a Lokalise plan that includes Audit Logs; availability was verified on Trial. The response intentionally excl
- List Branches
List one page of branches for a Lokalise project. This capability requires a Software project with Branching enabled; it is unavailable for other project types or projects with Branching disabled.
- List Keys
Search and return one cursor page of keys from a Lokalise project or branch. Translation, comment, and screenshot expansion is opt-in to keep responses small. Branch access requires a branch-enabled Software project.
- List Project Languages
List one page of languages configured for a Lokalise project or, when branch_name is supplied, for a branch. Branch access requires a compatible Software project with Branching enabled.
- List Projects
List projects available to the connected Lokalise API token, optionally filtered by team or exact project names. Include settings to discover whether a Software project has Branching enabled.
- List Translations
Search and return one cursor page of translations from a Lokalise project or branch by language, review state, task, or QA issue. Branch access requires a branch-enabled Software project.
- Update Keys
Batch update keys and their translations, including key metadata, translation content, review flags, and custom statuses, in one Lokalise project or branch. Requires a personal read/write API token and the project's Manage keys admin right.
- Update Translation
Update one translation's content and review or status flags in a Lokalise project or branch. Requires a personal read/write API token; a read-only token cannot perform this action. Branch targets additionally require a compatible Software p
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Lokalise.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Lokalise tools in chat.
What teammates see: by default, memories from Lokalise are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.