How to Use the Lokalise MCP in Claude Code

Q: How do I add Lokalise to Claude Code?

Use the command claude mcp add followed by the server URL. Once configured, you can run translation tasks directly from your terminal or CI environment.

Q: Can Claude Code handle Lokalise language lists?

Absolutely. Run listlanguages to see what is currently supported in your project. It's helpful for verifying your localization scope before a release.

Q: Does Claude Code work with Lokalise team members?

It does. Use listteammembers to audit access permissions in your CI scripts. This helps ensure your automated processes are running with the right account context.

Automate your CI/CD localization pipelines with Claude Code and Lokalise.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lokalise MCP to Claude Code

Create your Vinkius account to connect Lokalise to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Lokalise with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Claude Code manages Lokalise via CLI

Integrate your translation pipeline directly into your shell scripts. Claude Code uses `upload_file` to push your latest strings as part of your build process. It's built for headless execution. You can pipe the results of these tools into your logs to ensure your build pipeline has the most recent translations before deployment.

Programmatic translation access with Claude Code

Query your translation state without a GUI. Use `list_translations` to verify that your keys are populated before your tests run. It gives you total control over the data. You can script the entire process of checking key status, updating values, and pulling new bundles, all from your terminal.

CI/CD integration for Lokalise and Claude Code

Automate project creation by running `create_project` during your staging setup. It ensures every environment starts with the correct localization context. This setup removes the need for manual check-ins. Your pipeline handles the communication with Lokalise so your team can focus on shipping code.

Setup guide

Set up Lokalise MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see lokalise-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Lokalise transactions." It will automatically discover and invoke the available Lokalise tools.

Terminal

claude mcp add --transport http lokalise-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Lokalise MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "lokalise-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lokalise. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Lokalise now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Lokalise MCP in Claude Code

Use the command `claude mcp add` followed by the server URL. Once configured, you can run translation tasks directly from your terminal or CI environment.

Absolutely. Run `list_languages` to see what is currently supported in your project. It's helpful for verifying your localization scope before a release.

It does. Use `list_team_members` to audit access permissions in your CI scripts. This helps ensure your automated processes are running with the right account context.

Your translation data is encrypted in transit and processed only within your ephemeral session. We enforce strict endpoint authentication, ensuring that only your authorized tokens interact with your localization records.

Every action is logged in your terminal output. You can capture this data in your CI logs to audit exactly when keys were updated or files were downloaded.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript