Lara Translate MCP Server
The Lara Translate MCP Server enables AI applications to access professional-grade translation capabilities via the Model Context Protocol.
Text translation: Supports multi-language translation with automatic source language detection, context-aware translations, and selective translation of specific text blocks
Translation memory management: Create, update, delete, import TMX files, add/delete translation units, and check import job status
Enhanced quality control: Improve translations by providing context and custom instructions for tone, style, or domain-specific accuracy
Integration efficiency: Reduces computational overhead when paired with LLMs by handling translations separately
Flexible deployment: Available via NPX, Docker, or can be built from source
Supports running the MCP server in a Docker container, providing an isolated environment with all dependencies for the Lara Translate integration.
Enables running the MCP server directly through NPX, allowing users to execute the package without installing it locally.
Supports local development and package management for the MCP server through pnpm, which is used for installing dependencies and building the project.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Lara Translate MCP Servertranslate 'Hello, how are you?' from English to Spanish"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Lara Translate MCP Server
A Model Context Protocol (MCP) server for Lara Translate, enabling professional translation capabilities with support for language detection, context-aware translations, translation memories, and glossaries.
Lara leverages Translation Language Models (T-LMs) trained on billions of professionally translated segments, delivering domain-specific translations that capture cultural nuances and industry terminology that general-purpose LLMs often miss.
Quick Start
Pick your client below — no API keys needed, just log in through your browser.
Claude Desktop
Go to Settings > Connectors
Click Add Custom Connector
Enter the name:
LaraEnter the URL:
https://mcp-v2.laratranslate.com/v1Click Add, then click Connect
Log in with your Lara Translate credentials in the browser
Done — Lara Translate is now available in your conversations.
Cursor
Once Lara Translate is listed in the official Cursor plugin marketplace, install it from inside Cursor:
Open the plugin browser and search for Lara Translate.
Click Install.
The first time you use a Lara tool, your browser will open to authenticate.
In the meantime, or for manual installation, see the Client Setup Guide.
Claude Code
Once Lara Translate is listed in the official Claude Code plugin marketplace, install it from inside Claude Code:
/pluginSearch for Lara Translate and install. The first time you use a Lara tool, your browser will open to authenticate.
In the meantime, or for manual installation, see the Client Setup Guide.
Other Clients
For step-by-step OAuth setup on VS Code (GitHub Copilot), Windsurf, Cline, Continue, and more, see the Client Setup Guide.
If your client isn't listed, the general approach is to add the server URL (https://mcp-v2.laratranslate.com/v1) to your MCP config — the client will handle OAuth authentication automatically.
For a complete list of MCP-compatible clients, visit the official MCP clients page.
Verify It Works
After setup, test with a simple prompt:
Translate with Lara "Hello world" to SpanishYour client should invoke Lara Translate and return the translation.
Related MCP server: Jira MCP Server
Available Tools
Translation
Tool | Description |
| Translate text between languages with support for context, instructions, translation memories, glossaries, and multiple styles (faithful/fluid/creative) |
Language Detection
Tool | Description |
| Detect the language of a given text or array of texts |
| List all supported language codes |
Translation Memories
Tool | Description |
| List all translation memories in your account |
| Create a new translation memory |
| Update a translation memory's name |
| Delete a translation memory |
| Add a translation unit (source + target pair) to a memory |
| Delete a translation unit from a memory |
| Import a TMX file into a memory |
| Check the status of a TMX import job |
Glossaries
Tool | Description |
| List all glossaries in your account |
| Get details of a specific glossary |
| Create a new glossary |
| Update a glossary's name |
| Delete a glossary |
| Add or replace a term entry in a glossary |
| Delete a term entry from a glossary |
| Import entries from a CSV file into a glossary |
| Check the status of a glossary CSV import job |
| Export a glossary as CSV |
| Get the number of entries in a glossary |
Authentication
OAuth 2.0 (default)
This is the method used in the Quick Start above. You provide only the server URL in your client config — no API keys needed. Your client handles the OAuth flow automatically: it opens your browser, you log in with your Lara Translate credentials, and you're connected.
For per-client OAuth setup instructions, see the Client Setup Guide.
Access Key (alternative)
If you prefer to authenticate with API keys instead of browser login, you can pass your credentials directly in the client config. Get your Access Key ID and Secret from Lara Translate.
See the Access Key section in the Client Setup Guide for config examples.
Self-Hosting
Most users can connect to the hosted endpoint (https://mcp-v2.laratranslate.com/v1) using the Quick Start instructions above. The options below are for running the server yourself.
STDIO via NPX
Requires Node.js.
{
"mcpServers": {
"lara-translate": {
"command": "npx",
"args": ["-y", "@translated/lara-mcp@latest"],
"env": {
"LARA_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY_ID>",
"LARA_ACCESS_KEY_SECRET": "<YOUR_ACCESS_KEY_SECRET>"
}
}
}
}STDIO via Docker
Requires Docker.
{
"mcpServers": {
"lara-translate": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "LARA_ACCESS_KEY_ID",
"-e", "LARA_ACCESS_KEY_SECRET",
"translatednet/lara-mcp:latest"
],
"env": {
"LARA_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY_ID>",
"LARA_ACCESS_KEY_SECRET": "<YOUR_ACCESS_KEY_SECRET>"
}
}
}
}Building from Source
Node.js
git clone https://github.com/translated/lara-mcp.git
cd lara-mcp
pnpm install
pnpm run buildThen add to your MCP config:
{
"mcpServers": {
"lara-translate": {
"command": "node",
"args": ["<FULL_PATH_TO_PROJECT>/dist/index.js"],
"env": {
"LARA_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY_ID>",
"LARA_ACCESS_KEY_SECRET": "<YOUR_ACCESS_KEY_SECRET>"
}
}
}
}Docker
git clone https://github.com/translated/lara-mcp.git
cd lara-mcp
docker build -t lara-mcp .Then add to your MCP config:
{
"mcpServers": {
"lara-translate": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "LARA_ACCESS_KEY_ID",
"-e", "LARA_ACCESS_KEY_SECRET",
"lara-mcp"
],
"env": {
"LARA_ACCESS_KEY_ID": "<YOUR_ACCESS_KEY_ID>",
"LARA_ACCESS_KEY_SECRET": "<YOUR_ACCESS_KEY_SECRET>"
}
}
}
}Support
For issues with Lara Translate API: visit Lara Translate Support
For issues with this MCP server: open an issue on GitHub
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/translated/lara-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server