What kind of Lokalise API token do I need for this integration?

You need a Personal Access Token from your Lokalise account. Go to your profile settings, find the API Tokens section, and generate a new token with read/write access to projects. Keep this token secure as it grants full API access to your account.

How do I add a new translation key to my Lokalise project via the AI agent?

Use the `create_key` action with the project ID, key name (e.g., `homepage.welcome.title`), and optionally specify platforms, tags, and a description. The key will be created with the base language placeholder ready for translation.

Can I export all my translations in a specific format like JSON or YAML?

Yes! Use the `download_file` action and specify the `format` parameter (e.g., `json`, `yml`, `xliff`, `strings`, `xml`). You can also filter by specific languages or filenames to generate targeted export bundles.

Is it possible to add translations programmatically for multiple languages at once?

Yes. The `add_translation` action supports adding translations for one or more keys at once. You can also mark translations as fuzzy or reviewed to indicate their quality status in the workflow.

Lokalise MCP Server for VS Code Copilot 13 tools — connect in under 2 minutes

Name: Lokalise
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 13 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Lokalise and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Lokalise MCP Server

Connect your Lokalise account to any AI agent and take full control of your translation and localization workflows through natural conversation.

GitHub Copilot Agent mode brings Lokalise data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Project Management — List all translation projects, fetch detailed project metadata, and create new projects directly from the API
Key Management — Query translation keys with filters by platform, tags, or filenames, plus create and update keys programmatically
Translation Operations — Fetch translations for any key, add new translations with review/fuzzy flags, and manage multi-language content
File Import/Export — Upload localization files (JSON, YAML, XLIFF) and generate download bundles in any supported format
Team & Orders — List team members and their roles, plus inspect professional translation orders

The Lokalise MCP Server exposes 13 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Lokalise to VS Code Copilot via MCP

Follow these steps to integrate the Lokalise MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Lokalise

Ask Copilot: "Using Lokalise, help me...". 13 tools available

Why Use VS Code Copilot with the Lokalise MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Lokalise through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Lokalise + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Lokalise MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Lokalise MCP Tools for VS Code Copilot (13)

These 13 tools become available when you connect Lokalise to VS Code Copilot via MCP:

add_translation

Add translations to one or more keys

create_key

Create translation keys in a Lokalise project

create_project

Create a new Lokalise project

download_file

Generate a download bundle of translations

get_project

Get details of a specific Lokalise project

list_keys

List translation keys in a Lokalise project

list_languages

List languages in a Lokalise project

list_orders

List translation orders in your Lokalise account

list_projects

List all Lokalise projects

list_team_members

List all team members in your Lokalise account

list_translations

List translations for a key in a Lokalise project

update_key

Update an existing translation key

upload_file

Upload a localization file to a Lokalise project

Example Prompts for Lokalise in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Lokalise immediately.

"List all my Lokalise translation projects and show their current status."

"Create a new translation key 'checkout.success.message' in my Web App project for the web platform."

"Download all Portuguese (pt-BR) translations from my Mobile App project in JSON format."

Troubleshooting Lokalise MCP Server with VS Code Copilot

Common issues when connecting Lokalise to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Lokalise + VS Code Copilot FAQ

Common questions about integrating Lokalise MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.