MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Lokalise MCP Server

Name: Lokalise
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR ToolsFree for Subscribers

Automate translation and localization workflows via Lokalise — manage projects, keys, and translations directly from any AI agent.

Get MCP Server for AI Agents

Ask AI about this MCP Server

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

What is the Lokalise MCP Server?

The Lokalise MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Lokalise via 13 tools. Automate translation and localization workflows via Lokalise — manage projects, keys, and translations directly from any AI agent. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.

Built-in capabilities (13)

add_translationcreate_keycreate_projectdownload_fileget_projectlist_keyslist_languageslist_orderslist_projectslist_team_memberslist_translationsupdate_keyupload_file

Tools for your AI Agents to operate Lokalise

Ask your AI agent "List all my Lokalise translation projects and show their current status." and get the answer without opening a single dashboard. With 13 tools connected to real Lokalise data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.

Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.

Why teams choose Vinkius

One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.

Build your own MCP Server with our secure development framework →

Vinkius works with every AI agent you already use

…and any MCP-compatible client

Lokalise MCP Server capabilities

13 tools

add_translation

Add translations to one or more keys

create_key

Create translation keys in a Lokalise project

create_project

Create a new Lokalise project

download_file

Generate a download bundle of translations

get_project

Get details of a specific Lokalise project

list_keys

List translation keys in a Lokalise project

list_languages

List languages in a Lokalise project

list_orders

List translation orders in your Lokalise account

list_projects

List all Lokalise projects

list_team_members

List all team members in your Lokalise account

list_translations

List translations for a key in a Lokalise project

update_key

Update an existing translation key

upload_file

Upload a localization file to a Lokalise project

What the Lokalise MCP Server unlocks

Connect your Lokalise account to any AI agent and take full control of your translation and localization workflows through natural conversation.

What you can do

Project Management — List all translation projects, fetch detailed project metadata, and create new projects directly from the API
Key Management — Query translation keys with filters by platform, tags, or filenames, plus create and update keys programmatically
Translation Operations — Fetch translations for any key, add new translations with review/fuzzy flags, and manage multi-language content
File Import/Export — Upload localization files (JSON, YAML, XLIFF) and generate download bundles in any supported format
Team & Orders — List team members and their roles, plus inspect professional translation orders

How it works

1. Subscribe to this server
2. Enter your Lokalise API Token
3. Start managing your localization workflows from Claude, Cursor, or any MCP-compatible client

No more jumping between the Lokalise web console and your codebase. Your AI acts as a dedicated localization coordinator.

Who is this for?

Developers — instantly create translation keys, push new strings, and pull localized files without leaving the IDE
Product Managers — check translation progress across languages, review key counts, and monitor team activity
Localization Teams — automate bulk uploads, generate export bundles, and manage translation orders programmatically

Frequently asked questions about the Lokalise MCP Server

What kind of Lokalise API token do I need for this integration?

You need a Personal Access Token from your Lokalise account. Go to your profile settings, find the API Tokens section, and generate a new token with read/write access to projects. Keep this token secure as it grants full API access to your account.

How do I add a new translation key to my Lokalise project via the AI agent?

Use the create_key action with the project ID, key name (e.g., homepage.welcome.title), and optionally specify platforms, tags, and a description. The key will be created with the base language placeholder ready for translation.

Can I export all my translations in a specific format like JSON or YAML?

Yes! Use the download_file action and specify the format parameter (e.g., json, yml, xliff, strings, xml). You can also filter by specific languages or filenames to generate targeted export bundles.

Is it possible to add translations programmatically for multiple languages at once?

Yes. The add_translation action supports adding translations for one or more keys at once. You can also mark translations as fuzzy or reviewed to indicate their quality status in the workflow.