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 AutoGen 13 tools — connect in under 2 minutes

Name: Lokalise
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 13 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Lokalise as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="lokalise_agent",
            tools=tools,
            system_message=(
                "You help users with Lokalise. "
                "13 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Lokalise tools. Connect 13 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the Lokalise MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 13 tools from Lokalise automatically

Why Use AutoGen with the Lokalise MCP Server

AutoGen provides unique advantages when paired with Lokalise through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Lokalise tools to solve complex tasks

Role-based architecture lets you assign Lokalise tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Lokalise tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Lokalise tool responses in an isolated environment

Lokalise + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Lokalise MCP Server delivers measurable value.

Collaborative analysis: one agent queries Lokalise while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Lokalise, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Lokalise data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Lokalise responses in a sandboxed execution environment

Lokalise MCP Tools for AutoGen (13)

These 13 tools become available when you connect Lokalise to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

Common issues when connecting Lokalise to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Lokalise + AutoGen FAQ

Common questions about integrating Lokalise MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Lokalise tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.