An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Lokalise to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your entire translation pipeline through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 13 capabilities

We ship only the actions that matter.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 13 available through Lokalise.

  1. 01

    Get project

    Retrieves specific metadata and details for a single Lokalise project.

  2. 02

    List languages

    Shows all the languages currently configured within a specific project.

  3. 03

    List orders

    Fetches a list of all translation orders in your account.

  4. 04

    List translations

    Returns the available translations for a specific key in a project.

Capability set02 / 04

05-07

3 capabilities in this set.

Part of 13 available through Lokalise.

  1. 05

    Create key

    Adds a new translation key to your chosen Lokalise project.

  2. 06

    Create project

    Create a new Lokalise project

  3. 07

    Add translation

    Inserts new translations for one or more keys at once.

Capability set03 / 04

08-10

3 capabilities in this set.

Part of 13 available through Lokalise.

  1. 08

    Download file

    Generates and provides a download bundle for your translations.

  2. 09

    List keys

    Provides a list of all translation keys in a project.

  3. 10

    List projects

    Returns a list of every project in your Lokalise account.

Capability set04 / 04

11-13

3 capabilities in this set.

Part of 13 available through Lokalise.

  1. 11

    List team members

    Lists the members and roles within your Lokalise team.

  2. 12

    Update key

    Modifies the properties of an existing translation key.

  3. 13

    Upload file

    Sends a localization file directly to a Lokalise project.

Real work

What teams actually run

01

Automated String Deployment

A developer tells the agent to create a new key, which immediately makes it available for translators.

02

Localization Progress Checks

A product manager asks for the completion percentage of a specific language in a project.

03

Bulk File Syncing

An engineer uploads a new JSON localization file to a project using a single command.

04

Order Management

A localization lead checks the status of professional translation orders through the agent.

Automate a task

Put Lokalise to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Lokalise works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Lokalise to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1033ms average. Fast in production.

Lokalise is checked daily against the live service.

Daily averagePeak 1360ms
Oct 3Today
Fastest day
843ms
Slowest day
1360ms
14-day trend
Stable+2%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 13 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Lokalise, so you can see the experience inside your AI.

It does not authenticate your account with Lokalise. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Lokalise Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Lokalise capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "lokalise-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Lokalise in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Lokalise owners hand off.

This MCP is built for anyone managing software that needs to speak multiple languages.

  • 01

    Developers

    They use the agent to push new strings and pull files without leaving the IDE.

  • 02

    Product Managers

    They ask the agent for progress reports and key counts across different languages.

  • 03

    Localization Teams

    They automate bulk file uploads and manage translation orders through the agent.

FAQ

Questions Lokalise owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the MCP on Vinkius and enter your Lokalise API Token. Once connected, you can use it immediately in any MCP-compatible client like Claude or Cursor.

  • 02

    Which file formats are supported?

    The MCP supports common localization formats including JSON, YAML, and XLIFF for uploads and downloads.

  • 03

    Can I use this in my IDE?

    Yes, if you use an MCP-compatible IDE like Cursor or VS Code, you can manage your Lokalise keys and files without leaving your workspace.

  • 04

    Do I need to use the Lokalise website?

    While the website is still available, this MCP allows you to perform most management tasks through your AI agent instead.

  • 05

    Is my API token secure?

    Vinkius manages your credentials securely, so you don't have to worry about exposing your token in your local environment.

  • 06

    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.

  • 07

    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.

  • 08

    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.

  • 09

    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.

Explore

More in Productivity

Suggestions

Connect Lokalise to Claude, Cursor, ChatGPT & more