How to Use the Lokalise MCP in VS Code Copilot

Q: How do I configure the Lokalise MCP Server for VS Code Copilot?

Create a .vscode/mcp.json file in your repository and add the MCP server configuration. Once committed, your entire team can access the tools directly inside VS Code Copilot.

Q: Can VS Code Copilot upload my translation files to Lokalise?

Yes, you can instruct Copilot to call the uploadfile tool to upload your local translation files to your project.

Q: How do I verify active translation keys in VS Code Copilot?

Ask Copilot to run the listkeys tool. It queries your Lokalise project and displays the translation keys directly in the chat panel.

Q: Can I view my localization team members inside the editor?

Yes, the listteammembers tool pulls your team roster directly into the chat. You can verify who has access to your localization project without leaving the editor.

Automate translation management and sync Lokalise bundles directly inside VS Code Copilot.

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 VS Code Copilot

Create your Vinkius account to connect Lokalise to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate Key Creation Inside VS Code Copilot

The `create_key` tool registers translation keys to your localization project directly from your VS Code Copilot chat. When your team adds a new feature, Copilot writes the key and populates the default translation using `add_translation`. You can update existing strings without opening a browser. The `update_key` tool modifies keys on the fly, keeping your repository and localization database perfectly aligned.

Push and Pull Translation Files in Your Editor

The `upload_file` tool sends your local translation files straight to your localization project. Your team commits a new JSON file, and Copilot uploads it to the project with a simple chat command. To pull down completed translations, the `download_file` tool generates the bundle and drops the files into your workspace. This eliminates manual file exports and keeps your local builds up to date.

Manage Translation Projects with this MCP Server

The `list_projects` tool retrieves your active localization projects directly inside your editor. You can inspect project structures with `get_project` or create a new localization target using `create_project`. This MCP Server runs on a secure, zero-trust infrastructure. Your team can query `list_languages` to verify active locales or check team access using `list_team_members` directly from the chat window.

Setup guide

Set up Lokalise MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Lokalise MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Lokalise tools listed. Try asking: "List my recent Lokalise transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "lokalise-mcp": {
      "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 VS Code Copilot

Create a `.vscode/mcp.json` file in your repository and add the MCP server configuration. Once committed, your entire team can access the tools directly inside VS Code Copilot.

Yes, you can instruct Copilot to call the `upload_file` tool to upload your local translation files to your project.

Ask Copilot to run the `list_keys` tool. It queries your Lokalise project and displays the translation keys directly in the chat panel.

Yes, the `list_team_members` tool pulls your team roster directly into the chat. You can verify who has access to your localization project without leaving the editor.

All localization files and API tokens are processed in a secure, ephemeral V8 sandbox. This architecture guarantees that your translation data is never cached or exposed to third parties.

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