Lokalise Connector for AI agents.
13 live capabilities
Manage global translation projects and localization keys from your workspace.
Waiting for input…
Why people use Lokalise
Lokalise for Automated Translation Key Management
This Connector puts your entire Lokalise account into your AI client. Instead of manual clicks, you just ask your agent to create keys, update strings, or check project status. You get a unified workflow where your localization data lives where you actually work.
What Vinkius changes
You get a conversational interface for your entire localization backend.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
New feature launch
A dev needs to add 20 new strings.
- Real-world use case 02
Status check
A PM wants to know if the Spanish translation is done.
- Real-world use case 03
Bulk update
A localization lead needs to push a JSON file.
Complete set · 13capabilities
The complete Lokalise capability set.
These are the exact actions your AI can choose when you ask it to work with Lokalise.
01—04
4 capabilities in this set.
Part of 13 available through Lokalise.
- 01 Capability
Download file
Generate a download bundle of your translations. Use this to grab your final strings for any platform.
- 02 Capability
Get project
Fetch the metadata and details for a specific project. This gives you a quick overview of project status.
- 03 Capability
List keys
List all translation keys currently in a project. Use this to see every string that needs translating.
- 04 Capability
List languages
See all languages currently configured in a project. This helps you verify which regions are supported.
05—07
3 capabilities in this set.
Part of 13 available through Lokalise.
- 05 Capability
List orders
View all active and past translation orders in your account. Use this to track professional work.
- 06 Capability
List team members
View all members and their roles in your Lokalise account. This helps you manage who can edit your content.
- 07 Capability
List translations
Get the translations for a specific key. Use this to check how a single string looks in every language.
08—10
3 capabilities in this set.
Part of 13 available through Lokalise.
- 08 Capability
Upload file
Upload a localization file to a project. This lets you move entire JSON or XLIFF files into the system.
- 09 Capability
Add translation
Add translations to one or more keys. This helps you update multiple strings at once.
- 10 Capability
Create key
Create translation keys in a Lokalise project. This lets you register new strings without using the web dashboard.
11—13
3 capabilities in this set.
Part of 13 available through Lokalise.
- 11 Capability
Create project
Create a brand new localization project in your account. This is useful for starting new apps or websites.
- 12 Capability
Update key
Edit an existing translation key. This is how you change the name or metadata of a specific string.
- 13 Capability
List projects
See a full list of all your Lokalise projects. This is the quickest way to see your entire portfolio.
Set up in minutes
One URL. Then ask Lokalise to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Lokalise from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Lokalise, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Lokalise for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Lokalise URL.
- Step 03
Save and start
Save the connection and enable Lokalise in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"lokalise": {
"url": "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Lokalise
Open Agent mode in chat and ask: "Using Lokalise, help me...". 13 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"lokalise": {
"url": "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Lokalise
Ask Copilot: "Using Lokalise, help me...". 13 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"lokalise": {
"url": "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Lokalise
Open Cascade and ask: "Using Lokalise, help me...". 13 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"lokalise": {
"url": "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Lokalise
Ask Cline: "Using Lokalise, help me...". 13 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add lokalise --transport http "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Lokalise
Ask Claude: "Using Lokalise, show me...". 13 tools are ready
Where the request belongs
Work Lokalise can move forward.
This is for the dev who hates manual key entry, the product manager tracking dozens of languages, and the localization lead who needs to move files quickly without manual exports.
Software Engineer
Creates new translation keys and pushes updated strings directly from the IDE to keep the dev cycle moving.
Product Manager
Checks translation progress across multiple languages to ensure the marketing site is ready for launch.
Localization Specialist
Manages bulk file uploads and handles professional translation orders without clicking through dozens of dashboard menus.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsLocalazy (AI Translation & Localization API)
Manage software localization and translations via Localazy. list projects, import content, manage source keys, and handle glossary terms directly from your AI agent.
Transifex
Localize your projects efficiently using AI Agents with the official Transifex integration.
OneSky (App & Web Localization API)
Automate app and web localization via OneSky. manage project groups, track translation progress, and handle projects directly from your AI agent.
Weblate
Automate localization workflows via Weblate. manage projects, components, languages, and users directly from any AI agent.
Phrase (Software Localization API)
Manage software localization projects, locales, and translation keys directly through the Phrase API.
Smartling (Translation Workflow API)
Automate translation workflows via Smartling. manage projects, create jobs, upload content, and download translations directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep Lokalise connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Lokalise.
The practical details behind the request, access and result.
Can the Lokalise MCP help my developers manage translation keys?
Yes, it lets your AI agent create and update keys directly in your projects so developers don't have to leave their workspace.
How do I use the Lokalise MCP to check translation progress?
You can just ask your agent to list your projects or specific translations to get a real-time status update on your global rollout.
Can I upload translation files using the Lokalise MCP?
Yes, your agent can handle uploading files in formats like JSON, YAML, and XLIFF directly to your specified projects.
Does the Lokalise MCP support team management?
It does. You can use your agent to see who's on your team and what roles they have within your account.
Can I download translation bundles with this?
Yes, you can tell your agent to generate a download bundle for any supported format to get your strings ready for production.
Is the Lokalise MCP good for large scale localization?
It's ideal for it because it automates the repetitive tasks of key management and bulk file syncing that usually slow down big projects.
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.
One connection away
Give your agent a direct line to Lokalise.
Connect Lokalise once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available