Lokalise MCP. Manage keys and translations from your chat window.
Lokalise takes over your translation workflow. Connect this MCP to manage entire localization pipelines—from creating new keys to downloading finished files—all through natural conversation with your AI agent.
Give Claude and any AI agent real-world access
List all existing translation projects and create new ones with a single command.
Create, update, or list specific text keys across your entire project setup.
Fetch translations for a key, add new language versions, and review existing content flags.
Upload localization files (like JSON or YAML) to the project or generate structured download bundles in any format.
List team members' roles or check the status of professional translation orders.
Ask an AI about this
Waiting for input…
What AI agents can do with Lokalise: 13 Localization Tools
These tools let you control every aspect of translation management—from listing basic projects to generating final download bundles.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Lokalise MCPAdd Translation
Adds specified translations to one or more existing keys within a project.
Create Key
Creates entirely new translation keys inside your Lokalise project setup.
Create Project
Establishes a brand-new, dedicated localization project in the system.
Download File
Generates and prepares a download bundle of translations for you to retrieve.
Get Project
Retrieves detailed metadata about a specific, existing Lokalise project.
List Keys
Fetches a list of all translation keys available within a given project scope.
List Languages
Shows which languages are currently configured for your Lokalise project.
List Orders
Retrieves a list of professional translation orders associated with your account.
List Projects
Lists all the localization projects that currently exist under your Lokalise account.
List Team Members
Retrieves a roster of team members and their roles for administrative review.
List Translations
Shows all recorded translations for a single key within the project.
Update Key
Modifies existing translation keys to change their content or metadata.
Upload File
Uploads external localization files, such as JSON or XLIFF, into the project for processing.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Lokalise, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lokalise. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Localization workflows are a mess of tabs and copy-paste.
Today, updating translations for a global product means jumping between tools: the code editor to grab a key; a spreadsheet to manage language variants; and finally, the web console to execute the changes. This process is slow, error-prone, and requires constant context switching that grinds development momentum to a halt.
With this MCP, you talk directly to your AI agent. You ask it to handle the update. It executes the necessary calls—using tools like `update_key` or `add_translation`—and returns confirmation. The whole process stays in one conversation thread. You just get results.
Lokalise gives you control over your entire content pipeline.
Manual steps that vanish include navigating to the project list, fetching metadata using `get_project`, and manually checking team member roles via `list_team_members`. These administrative checks used to be a chore of clicks and dashboard reviews.
Now, you just ask. The agent retrieves the data for you. You aren't limited by the UI structure; you're limited only by how well you can articulate your needs.
What Lokalise MCP does for your AI
Need to handle a massive, multi-language launch? This connector lets you take full control of your product's localization process without leaving your coding environment. You talk to your AI agent, and it handles the API calls to Lokalise. Want to see what projects exist or get details on a specific one? Just ask.
Need to add fifty new strings across ten languages? It manages that complex data exchange for you. This means no more copying massive CSVs into separate web tabs. You can list all your translation keys and then tell the agent, 'Update this key with these new values.' The whole process is managed through natural conversation, making it feel like having a dedicated localization coordinator sitting right next to you.
All of this powerful functionality is available through Vinkius, connecting Lokalise directly to your preferred AI client.
019d75c9-ed31-739e-ae5d-834da7dad862 How to set up Lokalise MCP
The bottom line is that you guide the whole localization process using natural language, letting the MCP handle all the complex backend API interactions.
Subscribe to this MCP on Vinkius and provide your Lokalise API token.
Tell your AI agent what you need. For instance, 'List all active projects.'
Your agent executes the necessary calls and returns structured data—like a list of project names or available translation keys—directly into your conversation.
Who uses Lokalise MCP
This tool is for product owners and developers who are tired of manually juggling spreadsheets, web consoles, and codebases just to get a simple string updated. It's built for people whose daily job involves coordinating content across multiple languages.
You use it to instantly create translation keys or push new localized files directly from your IDE without switching context.
You check translation progress across different languages and monitor key counts using the agent, getting an immediate status report in chat.
You automate bulk uploads of files or generate export bundles for QA teams by simply describing the required format and language set.
Benefits of connecting Lokalise MCP
Stop switching between tabs. You can list projects or get details using the get_project tool, all within the conversation flow.
Keep developers in their IDE. Use create_key to instantly add new strings that need translation without leaving your code editor.
Automate content gathering. Upload localization files with upload_file, allowing you to process large volumes of data programmatically.
Track team progress easily. You can use list_team_members or check professional orders via list_orders to see who's working on what.
Simplify bulk exports. Generating a download bundle with the download_file tool means you get clean, structured files ready for QA.
Lokalise MCP use cases
Need to update fifty keys across three languages immediately.
The Product Manager asks the agent: 'Update the key 'login.button' with these new values.' The agent uses add_translation and update_key, ensuring all required language strings are changed correctly, which used to take hours of manual entry.
Launching a new product line requires dozens of new phrases.
The developer asks the agent to 'Create ten new keys for checkout flow.' The agent uses create_key repeatedly, populating all necessary strings in the project instantly so translators can start working.
Need a full export of all content changes from last month.
The localization team asks the agent to 'Download everything for Portuguese and German.' The agent uses download_file, giving them one clean, zip-ready bundle rather than multiple manual downloads.
Checking if a new feature requires keys in every language.
The PM asks the agent to 'List all translations for this key.' The agent uses list_translations and checks the status across all configured languages, giving an immediate compliance report.
Lokalise MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Manually checking project scope.
Opening the Lokalise web console, navigating to the project dashboard, and clicking through multiple tabs just to count keys or check status reports.
Just ask your agent: 'List all projects' using list_projects, then follow up with 'Get details for [Project Name]' using get_project. It keeps you in one chat window.
Updating keys via code snippets.
Hardcoding translation values directly into your application source files, which means every future change requires a full code push and manual review cycle.
Instead, use the agent to create_key or update_key. This keeps the source of truth centralized in Lokalise, making it easy for the team to manage.
Mixing up file formats.
Forgetting whether you need JSON, YAML, or XLIFF when uploading content and having to restart the entire import process.
Use upload_file with clear instructions about the format. If you're done, use download_file—the agent handles the required output structure.
When to use Lokalise MCP
You should use this MCP if your primary bottleneck is context switching. Specifically, if you find yourself moving between a code editor, a spreadsheet, and a dedicated web console just to manage text strings or localization assets. Use it to list projects, get key details, or update translations programmatically.
You don't need this if you are only performing ad-hoc tasks like checking one single string manually. For those simple checks, the native Lokalise UI is fine. But if your workflow involves bulk actions—like running upload_file, generating comprehensive bundles with download_file, or managing dozens of keys using create_key and update_key—this MCP saves you time and sanity.
Frequently asked questions about Lokalise MCP
How do I list all my projects using Lokalise MCP? +
You simply ask the agent to 'List all projects.' The agent uses list_projects and returns a comprehensive list of every project under your account, letting you see what's ready for work.
Can I bulk upload files with Lokalise MCP? +
Yes. You use the upload_file tool to send localization files like JSON or XLIFF directly into your project queue, handling large data sets in one go.
What if I need to change a key's value? +
You tell the agent exactly which key and what the new text should be. It then uses the update_key tool to modify that string across all relevant languages.
How do I get translated content for a specific feature? +
Use the agent to list translations via list_translations. This shows you every language and its current status for a single, identified key.
Is Lokalise MCP useful for developers? +
Absolutely. Developers love it because they can use the agent to run commands like create_key directly from their IDE chat window instead of needing to open a web browser tab.