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.

Lokalise MCP Server for Cursor 13 tools — connect in under 2 minutes

Name: Lokalise
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 13 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Lokalise and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "lokalise": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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

About Lokalise MCP Server

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

Cursor's Agent mode turns Lokalise into an in-editor superpower. Ask Cursor to generate code using live data from Lokalise and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

The Lokalise MCP Server exposes 13 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Lokalise to Cursor via MCP

Follow these steps to integrate the Lokalise MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Lokalise

Open Agent mode in chat and ask: "Using Lokalise, help me...". 13 tools available

Why Use Cursor with the Lokalise MCP Server

Cursor AI Code Editor provides unique advantages when paired with Lokalise through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Lokalise + Cursor Use Cases

Practical scenarios where Cursor combined with the Lokalise MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Lokalise MCP Tools for Cursor (13)

These 13 tools become available when you connect Lokalise to Cursor via MCP:

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

Example Prompts for Lokalise in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Lokalise immediately.

"List all my Lokalise translation projects and show their current status."

"Create a new translation key 'checkout.success.message' in my Web App project for the web platform."

"Download all Portuguese (pt-BR) translations from my Mobile App project in JSON format."

Troubleshooting Lokalise MCP Server with Cursor

Common issues when connecting Lokalise to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Lokalise + Cursor FAQ

Common questions about integrating Lokalise MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.