Lokalise MCP Tool
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Lokalise MCP Tool Add key 'welcome_text' with value 'Welcome' to project 'SaaS-App' for web"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Lokalise MCP Tool
A Minimal Command-line Program (MCP) server for adding translation keys to your Lokalise projects, designed for integration with Cursor or standalone use.
π¦ Installation
# For MCP usage (global installation)
npm install -g lokalise-mcp-server
# For library usage (project dependency)
npm install lokalise-mcp-serverNPM Package: https://www.npmjs.com/package/lokalise-mcp-server
Related MCP server: tolgee-mcp
πΌοΈ MCP Flow Diagram

This diagram illustrates the Model Context Protocol (MCP) flow between Cursor, your MCP server, and Lokalise.
β‘οΈ Usage (Quick Start with Cursor MCP)
Option 1: NPM Package (Recommended)
π οΈ Add this to your mcp.json (or configure via Cursor UI):
{
"mcpServers": {
"lokalise": {
"command": "npx",
"args": ["-y", "lokalise-mcp-server"],
"env": {
"LOKALISE_API_KEY": "your_actual_api_key"
}
}
}
}π Reload Window. It will automatically use the npm package.
Option 2: Docker (Alternative)
No need to run Docker or Podman manually!
π³ Make sure Docker or Podman is installed and running.
π οΈ Add this to your
mcp.json(or configure via Cursor UI):{ "mcpServers": { "lokalise": { "command": "docker", // podman "args": [ "run", "--rm", "-i", "-e", "LOKALISE_API_KEY", "rafee03/mcp-lokalise:latest" ], "env": { "LOKALISE_API_KEY": "your_actual_api_key" } } } }You can use
podmaninstead ofdockerif you prefer.Cursor will automatically pull and run the image as needed.
π Restart Cursor. It will handle everything for you.
π How to Use in Cursor
This tool takes these inputs:
projectName (required): The name of your Lokalise project (e.g.,
SpaceX).keys (required): An array of objects, each with:
keyName (required): The translation key (e.g.,
hello)defaultValue (optional): The default translation value (e.g.,
Hello)platforms (optional): The platforms this key applies to (e.g.,
web,ios)
Example:
I want to add two keys, one is hello and another one is bye. their default values are Hello and Goodbye. both are in web platform. the project is spaceX
Cursor will automatically convert this to the correct input for the MCP tool.

π Project Files
TypeScript Source Files (src/):
src/mcp-server.ts: The main MCP server entry point for Cursor integration.
src/mcp.ts: Shared logic for interacting with the Lokalise API (used by the server).
src/server.ts: (Optional) HTTP server version (not required for Cursor).
src/add-key.ts: (Optional) CLI tool for adding a key interactively (not required for Cursor).
Compiled JavaScript Files (dist/):
dist/mcp-server.js: Compiled MCP server.
dist/mcp.js: Compiled API logic.
dist/server.js: Compiled HTTP server.
dist/add-key.js: Compiled CLI tool.
Other Files:
tsconfig.json: TypeScript configuration.
Dockerfile: For building the Docker image of the MCP server.
package.json: Project dependencies and scripts.
README.md: This documentation file.
π οΈ Setup (For Local Development or Customization)
1. π₯ Clone the Repository
git clone https://github.com/mdrafee03/mcp-lokalise.git
cd mcp-lokalise2. π¦ Install Dependencies
npm install3. π¨ Build the Project
npm run build4. π Set Your Lokalise API Key
In your MCP config (recommended for Cursor)
{
"mcpServers": {
"lokalise": {
"command": "node",
"args": ["{directory-of-the-project}/dist/mcp-server.js"],
"env": {
"LOKALISE_API_KEY": "your_actual_api_key"
}
}
}
}Available Scripts
npm run build- Compile TypeScript to JavaScriptnpm run dev- Run the MCP server in development mode with tsxnpm run server- Run the HTTP server in development mode with tsxnpm run add-key- Run the CLI tool in development mode with tsxnpm start- Run the compiled MCP server from dist/
Requirements
Node.js 22+ recommended
TypeScript 5.8+
MCP protocol via @modelcontextprotocol/sdk
License
MIT
Available Tools
1 tooladd_lokalise_keysC
Add multiple translation keys to a Lokalise project using structured input
Inputs: projectName (required), keys (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as adding translation keys to a Lokalise project.
A single tool inherently has perfect naming consistency. The tool name 'add_lokalise_keys' follows a clear verb_noun pattern and is descriptive of its function.
A single tool for a Lokalise MCP server is too few for typical translation management workflows. Lokalise involves operations like creating, updating, deleting, and fetching keys or translations, so one tool feels incomplete and thin for the domain.
The tool set is severely incomplete for Lokalise translation management. It only supports adding keys, missing essential operations like retrieving, updating, or deleting keys, managing translations, or handling projects, which will cause significant agent failures.
Maintenance
Related MCP Connectors
MCP server for Crowdin β projects, files, strings, translation progress, tasks, and members.
Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.
MCP server for Translation Services
MCP server for LingoHub β localization projects, resources, exports and repository pushes.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables users to manage translations for their applications through SimpleLocalize's localization platform via natural language prompts in Cursor.73MIT
- AlicenseBqualityDmaintenanceAn MCP server that wraps the Tolgee localization platform API, enabling LLMs to manage translation projects, keys, translations, languages, and related workflows.27MIT
- FlicenseBqualityDmaintenanceAn MCP server for managing Lokalise translations, enabling creation, retrieval, and deletion of translation keys.3-
- AlicenseNot gradedqualityCmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.1MIT