Skip to content
Weavz
Menu
Lokalise

Lokalise MCP integration

Manage Lokalise localization projects, keys, languages, and file imports or exports.

Sign in, add Lokalise in Apps, then choose the account your AI can use.

9 tools
1 trigger
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Tools

Name
list_projects

List Lokalise projects visible to the token.

get_project

Get details for a Lokalise project.

list_languages

List languages configured in a Lokalise project.

list_keys

List Lokalise keys with optional cursor pagination and translation payloads.

get_key

Get a single Lokalise key by numeric key ID.

create_key

Create one Lokalise key, optionally with an initial translation.

update_key

Update Lokalise key metadata such as name, description, and platforms.

upload_file

Upload a bounded text localization file to Lokalise. Provide textual JSON, YAML, PO, strings, or similar content explicitly.

download_file

Start a Lokalise file download and return the bundle URL or async process payload.

Triggers

Name
new_key

Poll Lokalise keys and emit keys first seen after the trigger baseline.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('lokalise', 'list_projects', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'lokalise',
  input: { /* ... */ },
})

Related Integrations

Works well with

Frequently Asked Questions

Is there a Lokalise MCP server through Weavz?

Yes. Add the Lokalise integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 9 Lokalise actions.

What can an AI agent do with Lokalise?

Available actions include List Projects, Get Project, List Languages, List Keys, Get Key, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.

How do I connect Lokalise to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Lokalise, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.

Can I use Lokalise through an API or SDK?

Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.

What authentication does Lokalise require?

The catalog lists an API key for Lokalise. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.

How do I review sensitive Lokalise actions?

Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.

What limits or costs apply to Lokalise?

Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.

What Lokalise triggers are available?

The catalog lists 1 triggers, including New Key. Configure the trigger and your event handler before using incoming events to start work.

Connect Lokalise in minutes

Get 20,000 free action executions every month. No credit card required.