mcp-lokalise-server
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., "@mcp-lokalise-server create a translation key 'home_title' with English and Spanish translations"
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.
MCP Lokalise Server
A Model Context Protocol (MCP) server for managing Lokalise translations.
Features
✅ Create translation keys with multiple language translations
✅ Get specific translation key details by name
✅ Delete translation keys
Related MCP server: i18n-mcp
Installation
npm installUsage
The server can be used with any MCP-compatible client. It provides three main tools:
1. create_lokalise_key
Create a new translation key with translations:
{
"key_name": "my_new_key",
"translations": {
"en": "Hello World",
"de": "Hallo Welt"
}
}2. get_lokalise_key
Get details for a specific translation key by name:
{ "key_name": "my_key" }3. delete_lokalise_key
Delete a translation key by ID:
{ "key_id": "123456789" }Configuration
Create your API token here: https://app.lokalise.com/profile#apitokens
The server uses environment variables for configuration:
Environment Variables
LOKALISE_PROJECT_ID- Your Lokalise project IDLOKALISE_API_TOKEN- Your Lokalise API tokenLOKALISE_PLATFORMS- Comma-separated platforms (default:web)
MCP Client Configuration
Add to your MCP client configuration:
{
"mcpServers": {
"lokalise": {
"command": "node",
"args": ["/path/to/mcp-lokalise-server/index.js"],
"env": {
"LOKALISE_PROJECT_ID": "your-project-id",
"LOKALISE_API_TOKEN": "your-api-token",
"LOKALISE_PLATFORMS": "web"
}
}
}
}Available Tools
3 toolscreate_lokalise_keyB
Create a new translation key in Lokalise with translations
Inputs: key_name (required), translations (required).
delete_lokalise_keyB
Delete a translation key from Lokalise
Inputs: key_id (required).
get_lokalise_keyA
Get a specific translation key from Lokalise by name
Inputs: key_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools are clearly distinct: create, delete, and get are non-overlapping operations on translation keys.
All tools follow the exact pattern 'verb_lokalise_key' with consistent snake_case naming.
With only 3 tools, the server is very focused but borderline thin for a typical scope; however, it fits a minimal key management surface.
Missing essential operations like updating or listing keys, which creates significant gaps for common workflows.
Related MCP Connectors
MCP server for Crowdin — projects, files, strings, translation progress, tasks, and members.
MCP server for LingoHub — localization projects, resources, exports and repository pushes.
MCP server for Translation Services
Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn 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.113 npm4ISC
- AlicenseAqualityCmaintenanceMCP server for managing i18n JSON translation files. Provides Claude with structured read/write access to translation files for adding keys, checking coverage, and finding duplicates.1234 npm1MIT

kilo-dev-mcp-serverofficial
AlicenseNot gradedqualityFmaintenanceAn MCP server for internationalization (i18n) tasks, providing tools to translate, move, list, and remove translation keys in JSON files for the Kilo Code extension.24MIT- AlicenseNot gradedqualityCmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.1MIT