Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

MCP Server for Lara Translate API, enabling powerful translation capabilities with support for language detection and context-aware translations.

README.md

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.

![License](https://github.com/translated/lara-mcp/blob/main/LICENSE) ![Docker Pulls](https://hub.docker.com/r/translatednet/lara-mcp) ![npm downloads](https://www.npmjs.com/package/@translated/lara-mcp)

Quick Start

Pick your client below — no API keys needed, just log in through your browser.

Claude Desktop

  1. Go to Settings > Connectors
  2. Click Add Custom Connector
  3. Enter the name: Lara
  4. Enter the URL: https://mcp-v2.laratranslate.com/v1
  5. Click Add, then click Connect
  6. 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:

  1. Open the plugin browser and search for Lara Translate.
  2. Click Install.
  3. 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:

/plugin

Search 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 Spanish

Your client should invoke Lara Translate and return the translation.

---

Available Tools

Translation

| Tool | Description | |------|-------------| | translate | Translate text between languages with support for context, instructions, translation memories, glossaries, and multiple styles (faithful/fluid/creative) |

Language Detection

| Tool | Description | |------|-------------| | detect_language | Detect the language of a given text or array of texts | | list_languages | List all supported language codes |

Translation Memories

| Tool | Description | |------|-------------| | list_memories | List all translation memories in your account | | create_memory | Create a new translation memory | | update_memory | Update a translation memory's name | | delete_memory | Delete a translation memory | | add_translation | Add a translation unit (source + target pair) to a memory | | delete_translation | Delete a translation unit from a memory | | import_tmx | Import a TMX file into a memory | | check_import_status | Check the status of a TMX import job |

Glossaries

| Tool | Description | |------|-------------| | list_glossaries | List all glossaries in your account | | get_glossary | Get details of a specific glossary | | create_glossary | Create a new glossary | | update_glossary | Update a glossary's name | | delete_glossary | Delete a glossary | | add_glossary_entry | Add or replace a term entry in a glossary | | delete_glossary_entry | Delete a term entry from a glossary | | import_glossary_csv | Import entries from a CSV file into a glossary | | check_glossary_import_status | Check the status of a glossary CSV import job | | export_glossary | Export a glossary as CSV | | get_glossary_counts | 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 build

Then 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

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Other servers.