lara-mcp
A Model Context Protocol (MCP) server for Lara Translate, enabling professional translation capabilities with support for language detection, context-aware translations, translation memories, and…
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/translated/lara-mcp with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/translated/lara-mcp'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/translated--lara-mcp)HTML
<a href="/listings/translated--lara-mcp"><img src="/api/listings/translated--lara-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
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](docs/client-setup.md#cursor).
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](docs/client-setup.md#claude-code).
Other Clients
For step-by-step OAuth setup on **VS Code (GitHub Copilot)**, **Windsurf**, **Cline**, **Continue**, and more, see the **[Client Setup Guide](docs/client-setup.md)**.
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](https://modelcontextprotocol.io/clients).
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.
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 334 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # Lara Translate MCP Server
- A Model Context Protocol (MCP) server for [Lara Translate](https://laratranslate.com/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.
- [](https://github.com/translated/lara-mcp/blob/main/LICENSE)
- [](https://hub.docker.com/r/translatednet/lara-mcp)
- [](https://www.npmjs.com/package/@translated/lara-mcp)
- ## Quick Start
- Pick your client below — no API keys needed, just log in through your browser.
- > The previous URL, https://mcp-v2.laratranslate.com/v1, keeps working: existing connectors need no change.
- ### Claude Desktop
- 1. Go to **Settings** > **Connectors**
- 2. Click **Add Custom Connector**
- 3. Enter the name: `Lara`
- 4. Enter the URL: `https://mcp.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
- Add to `~/.cursor/mcp.json`:
- ```json
- {
- "mcpServers": {
- "lara-translate": {
- "url": "https://mcp.laratranslate.com/v1"
- }
- }
- }
- ```
- Restart Cursor. The first time you use a Lara tool, your browser will open to authenticate.
- Full instructions: [Client Setup Guide](docs/client-setup.md#cursor).
- ### Claude Code
- ```bash
- claude mcp add --transport http lara-translate https://mcp.laratranslate.com/v1
- ```
- Then run `/mcp` inside Claude Code to log in through your browser.
- Full instructions: [Client Setup Guide](docs/client-setup.md#claude-code).
- ### Other Clients
- For step-by-step OAuth setup on **VS Code (GitHub Copilot)**, **Windsurf**, **Cline**, **Continue**, and more, see the **[Client Setup Guide](docs/client-setup.md)**.
- If your client isn't listed, the general approach is to add the server URL (`https://mcp.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](https://modelcontextprotocol.io/clients).
- ### 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](#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](docs/client-setup.md)**.
- ### 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](https://developers.laratranslate.com/docs/getting-started#step-3---configure-your-credentials).
- See the [Access Key section in the Client Setup Guide](docs/client-setup.md#alternative-access-key-authentication) for config examples.
- ---
- ## Self-Hosting
- Most users can connect to the hosted endpoint (`https://mcp.laratranslate.com/v1`) using the [Quick Start](#quick-start) instructions above. The options below are for running the server yourself.
- ### STDIO via NPX
- Requires [Node.js](https://nodejs.org/) 22.23.4 or later (the `engines` field of the published package). Only needed to run the server locally: the hosted endpoint above needs no installation.
- ```json
- {
- "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](https://www.docker.com/).
- ```json
- {
- "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
- Requires Node.js 22.23.4 or later and pnpm.
- ```bash
- git clone https://github.com/translated/lara-mcp.git
- cd lara-mcp
- pnpm install
- pnpm run build
- ```
- Then add to your MCP config:
- ```json
- {
- "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
- ```bash
- git clone https://github.com/translated/lara-mcp.git
- cd lara-mcp
- docker build -t lara-mcp .
- ```
- Then add to your MCP config:
- ```json
- {
- "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>"
- }
- }
- }
- }
- ```
- ---
- ## Usage Metrics
- The server reports usage events to Lara so we can see which tools and options
- are used and which problems users run into. Usage metrics are **on by default**.
- They are **pseudonymous**, not anonymous: each event is tied to your Lara account
- id.
- **Events:** an `auth_success` the first time your credentials are accepted, a
- `call_success` / `call_error` per tool call (`quota_exceeded` instead of
- `call_error` when the account is out of quota), and an `auth_fail` when Lara
- rejects your credentials (sent without an account id when the key never worked).
- **What is sent:**
- - your Lara account id (`acc_...`) and the server version;
- - the tool name, how long the call took, and how many characters were translated;
- - for `translate`: the source and target language tags, the options you used,
- and how many text blocks, glossaries, memories and instructions the call had
- (how many — never which);
- - the kind of client (`claude`, `claude-code`, `chatgpt`, `cursor`, `codex`,
- `vscode` or `other`) and its version number;
- - the transport (`stdio` / `http`), operating system and Node.js version;
- - on errors: an error category, the HTTP status and error type Lara answered
- with, and the names of invalid arguments.
- **What is never sent:** the text you translate or its translation, your access
- key id and secret, glossary and memory ids, instructions, context, error
- messages, raw client names or user agents.
- An installation id (a random UUID, tied to nothing) is generated the first time
- an event is sent and kept at `~/.lara/installation-id` — set `LARA_HOME` to move
- it. It identifies this installation to the metrics backend, never you.
- ### Opting out
- **Per call:** a `translate` call with `no_trace: true` (Lara's own privacy flag)
- reports nothing at all — no event of any kind is sent for that call.
- **Entirely:** set `DO_NOT_TRACK` to `1`, `true` or `yes` and nothing is
- measured, queued, written to disk or sent:
- ```json
- {
- "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>",
- "DO_NOT_TRACK": "1"
- }
- }
- }
- }
- ```
- Metrics never block, slow down or fail a translation: events are batched, sent
- in the background, and a monitoring backend that is down is ignored.
- ---
- ## Support
- - For issues with Lara Translate API: visit [Lara Translate Support](https://support.laratranslate.com)
- - For issues with this MCP server: open an issue on [GitHub](https://github.com/translated/lara-mcp/issues)
- ## Lara Think
- Select Lara Think with `reasoning: true` on the `translate` tool. Choose Low,
- Medium or High with `reasoning_effort: "low" | "medium" | "high"`. Think defaults
- to **high** when the level is omitted. Without reasoning, Lara Base is used.
- A level requires `reasoning: true`; other combinations are rejected before the API call.
- ```json
- {"text":[{"text":"Hello","translatable":true}],"target":"it","reasoning":true,"reasoning_effort":"medium"}
- ```
- Think can take substantially longer. Existing timeout options still apply.
- When the MCP client supplies a `progressToken`, Lara Think streaming updates are
- forwarded as `notifications/progress`, without translation text or a percentage.
- These updates do not guarantee a longer client timeout; configure the client's
- request timeout separately.
- If Lara reports a reasoning fallback, the translation is retained and
- `warnings.reasoning.applied: false` and an explanatory text warning are returned.
- Absence of feedback does not prove which reasoning level ran internally.
- Usage metrics are enabled by default and can be disabled as described in Usage Metrics above.
- When enabled, they include the requested effective level and reported fallback, never source text.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.