This feature is in beta.
This guide shows you how to connect the Lokalise MCP Server to your tools or AI agents and start using it right away. The setup is simple, and you only need your Lokalise API token to get started.
How to set up the Lokalise MCP Server
Different MCP-compatible tools (AI agents, IDEs, orchestration platforms, etc.) have their own way of adding MCP servers, but the setup process is usually the same everywhere:
Find the place where the tool lets you add an MCP server or edit MCP configuration.
Create a new MCP server entry pointing to a Lokalise endpoint.
Add your Lokalise API token under the
apikeyheader.You can generate a new Lokalise API token in your Profile settings > API tokens.
Save the configuration so your tool/agent can detect the capabilities.
Below is the standard configuration you can use in any MCP-compatible environment.
Configurations
The Lokalise MCP Server provides two separate toolkits: Project management and Software development. You may need one or both, depending on which actions you want your agent to perform. Some actions require the PM toolkit, others require the SD toolkit.
A full table showing which action belongs to which toolkit is available below.
Project management toolkit configuration
"lokalise_pm": {
"type": "http",
"url": "https://mcp.lokalise.com/mcp/project-management",
"headers": {
"x-tester-key": "35DFAFD2-CE21-4D3E-860A-ADFBF9C88849",
"apikey": "[Enter-your-API-key-here]",
"accept": "application/json, text/event-stream"
}
}
Software development toolkit configuration
"lokalise_sd": {
"type": "http",
"url": "https://mcp.lokalise.com/mcp/software-development",
"headers": {
"x-tester-key": "35DFAFD2-CE21-4D3E-860A-ADFBF9C88849",
"apikey": "[Enter-your-API-key-here]",
"accept": "application/json, text/event-stream"
}
}
Replace [Enter-your-API-key-here] with your actual Lokalise API Key.
Example: Setting up the MCP server in Cursor
Open Cursor Settings.
Go to Tools & MCP.
Find the MCP configuration (JSON file) section.
Add the configurations to your MCP JSON file.
Using the MCP server
After you save the configuration:
Open a new conversation with an agent.
Ask it to use the Lokalise MCP server.
The agent will automatically detect the available Lokalise tools and perform actions in Lokalise on your behalf.
No extra commands or setup needed; the agent understands everything from the MCP configuration.
Frequently asked questions
What is the MCP Server and why use it?
Teams are adopting AI agents and automation tools to speed up localization. But connecting these tools to Lokalise usually means writing custom scripts and dealing with the API — which takes time and engineering skills.
The Lokalise MCP Server solves this by giving AI agents and internal tools a clear, structured way to work with Lokalise without manual scripting.
Who can use the Lokalise MCP server?
Any Lokalise team that’s on a plan with API access can use the MCP Server. If your team’s plan includes API access, you’re good to go.
What kind of API token do I need?
If you want the MCP Server to create, update, or upload anything in Lokalise (like creating a project, uploading files, adding tasks, and so on) you must use a read/write API token. A read-only token won't work for actions that change data.
Token permissions follow the user
API tokens in Lokalise always work in the context of the user who created them. It means:
If the user doesn’t have access to a project, the token won’t have access either.
If the user is not allowed to perform an action (like uploading files), the token also won’t be allowed.
If the user has limited project permissions, the token will inherit those limits.
So before using the MCP Server, make sure the user who generates the token has the right permissions for the tasks you want to automate. Learn more about permissions in the Contributors article.
Are there any limits?
Yes — the MCP Server uses the Lokalise API under the hood. This means all API rate limits and restrictions also apply to MCP.
What actions can I complete with the Lokalise MCP Server?
The Lokalise MCP Server currently provides two toolkits:
Project management
Software development
Different actions rely on different toolkits, so make sure you’ve enabled the right configuration(s) from the section above. These two toolkits cover most common automation tasks, and more (including translator-focused ones) will be added over time.
You don’t need to tell your agent which toolkit or action to use; it will automatically pick the correct one based on your prompt.
Description | Use case | Toolkit |
List all projects | View project portfolio and status | project-management |
Create a new project | Initialize new localization project | project-management |
Get project with statistics | Monitor project health & progress | project-management |
Update project settings | Adjust project configuration | project-management |
List project contributors | View project contributors with access level details | project-management |
Add a project contributor | Staff the project | project-management |
Update contributor role/permissions | Adjust contributor’s responsibilities | project-management |
Import contributors from another project | Quickly staff similar projects | project-management |
List project languages | View localization scope | project-management |
Add target languages | Expand project scope | project-management |
List all tasks | Track work assignments | project-management |
Create task | Assign translation work | project-management |
Update task (deadline/assignee) | Adjust assignments | project-management |
Get task details & progress | Monitor task completion | project-management |
Get key count & statistics | Monitor content volume | project-management |
List translation orders | Track outsourced work | project-management |
Create translation order | Request professional translation | project-management |
Get specific team details | Review team translations | project-management |
List all keys | Verify key exists before using in code, get all translations | project-management |
Filter untranslated keys | Find missing translations blocking deployment | project-management |
Filter by platform | Get platform-specific keys for current build | project-management |
Filter by filename | Find keys from specific source files | project-management |
Filter by tags | Find feature-specific keys | project-management |
Search by key nam | Find specific keys by name pattern | project-management |
Get specific key details | Inspect translations, plural forms, and context for a key | project-management |
Get task details & progress | Monitor task completion | software-development |
Get project details with statistics | Check translation progress %, QA issues count, release readiness | software-development |
Filter untranslated keys | Find missing translations blocking deployment | software-development |
Filter by platform | Get platform-specific keys for current build | software-development |
Filter by filename | Find keys from specific source files | software-development |
Filter by tags | Find feature-specific keys | software-development |
Search by key name | Find specific keys by name pattern | software-development |
Get specific key details | Inspect translations, plural forms, and context for a key | software-development |
|
|
|

