MCP Lokalise MCP Server

A Model Context Protocol (MCP) server for managing Lokalise translation keys with TypeScript support

Local serverstdioTypeScript

What is the MCP Lokalise MCP server?

If you want an AI assistant working directly with MCP Lokalise, the mcp lokalise mcp server is the bridge. A Model Context Protocol (MCP) server for managing Lokalise translation keys with TypeScript support.

What MCP Lokalise does

A Minimal Command-line Program (MCP) server for adding translation keys to your Lokalise projects, designed for integration with Cursor or standalone use.

Tools it exposes

Once connected, the assistant can call this tool directly:

  • Requirements — The Requirements tool exposed by this server

Installing the mcp lokalise mcp server

The server is distributed via npm as lokalise-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: LOKALISE_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Lokalise sits in that group, and the shape of its toolset — Requirements — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by mdrafee03, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp lokalise mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.

How to install the MCP Lokalise MCP server

{
  "mcpServers": {
    "lokalise": {
      "command": "npx",
      "args": ["-y", "lokalise-mcp-server"],
      "env": {
        "LOKALISE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LOKALISE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Lokalise to Requirements.

Frequently asked questions

It connects MCP Lokalise to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Requirements) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Lokalise directly.