Lokalise MCP Tool
An MCP server that enables users to add translation keys to Lokalise projects using natural language through Cursor or standalone interfaces. It allows for the specification of project names, translation keys, default values, and target platforms.
README
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-server
NPM Package: https://www.npmjs.com/package/lokalise-mcp-server
š¼ļø 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.
- You can use
-
š 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)
- keyName (required): The translation key (e.g.,
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-lokalise
2. š¦ Install Dependencies
npm install
3. šØ Build the Project
npm run build
4. š 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.