Log inSubmit server
Lara MCP logo

Lara MCP

by translated

Connects MCP clients to Lara Translate for translation, language detection, translation memories, and glossaries.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Lara MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "translated-lara-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@translated/lara-mcp@latest"
      ],
      "env": {
        "LARA_ACCESS_KEY_ID": "YOUR_VALUE_HERE",
        "LARA_ACCESS_KEY_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

translated/lara-mcp connects MCP-compatible clients to the Lara Translate API through a hosted HTTP endpoint or a self-hosted stdio process. Its tools cover translation, language detection, supported-language lookup, translation-memory management, and glossary operations. The translate tool accepts context, instructions, memories, glossaries, and faithful, fluid, or creative styles. Reach for it when an agent needs Lara Translate’s account resources or terminology controls alongside ordinary translation requests.

Use cases

  • Translate product or support content with contextual instructions
  • Detect languages across batches of text
  • Apply translation memories to recurring localization work
  • Manage terminology through Lara glossaries
  • Import TMX memories or CSV glossary entries

Key features

  • Context-aware translation with three style options
  • Language detection for individual or multiple texts
  • Translation-memory creation and TMX import
  • Glossary management with CSV import and export
  • Hosted OAuth and self-hosted access-key authentication

Tools22

What Lara MCP lets your agent do. Expand a tool for its parameters.

Self-reported~311 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

23/24 checks healthy over the last 86d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 0High 1Medium 0Low 0

Scanned 2d ago via OSV.dev · @translated/lara-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars100Stargazers on the source repository.
npm downloads2.7kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed22Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Lara MCP works

What translated/lara-mcp MCP server does

translated/lara-mcp exposes Lara Translate through the Model Context Protocol. It supports direct text translation, language detection for one or more text values, and lookup of supported language codes. Translation requests can include contextual information, instructions, translation memories, glossaries, and one of three styles: faithful, fluid, or creative.

The server also provides account-level operations for translation memories and glossaries. Memories can be created, renamed, removed, populated with source-and-target translation units, or loaded from TMX files. Glossaries can be created, renamed, deleted, inspected, populated with term entries, imported from CSV, exported as CSV, and checked for entry counts.

How it works

The hosted service is available at https://mcp.laratranslate.com/v1. Clients connect to that URL and authenticate through OAuth 2.0 in a browser using Lara Translate credentials. Existing connectors using https://mcp-v2.laratranslate.com/v1 continue to work.

Access-key authentication is also supported. In that mode, the client configuration supplies a Lara access key ID and secret rather than relying on browser login. Self-hosted deployments communicate with the MCP client over stdio and call the Lara Translate API with those credentials.

Usage metrics are enabled by default. Reported events include authentication results and per-tool success or error events. Metrics include account and request metadata such as tool name, timing, character counts, selected language tags, client information, transport, operating system, and Node.js version. Translated text, translations, credentials, glossary and memory IDs, instructions, context, and raw client identifiers are excluded from the listed metrics.

Setup and configuration

For a hosted connection, add https://mcp.laratranslate.com/v1 to the MCP client. Claude Desktop uses its custom connector settings; Cursor accepts the URL in ~/.cursor/mcp.json; Claude Code can add it with an HTTP transport command. VS Code with GitHub Copilot, Windsurf, Cline, Continue, and other clients use their respective MCP configuration and OAuth flow.

A local Node.js deployment uses the @translated/lara-mcp@latest package through npx and requires Node.js 22.23.4 or later. Docker is another stdio option, using the translatednet/lara-mcp:latest image. Building from source requires Node.js 22.23.4 or later and pnpm; the project can also be built into a Docker image.

Self-hosted configurations must provide LARA_ACCESS_KEY_ID and LARA_ACCESS_KEY_SECRET. The hosted endpoint does not require API keys in the client configuration when OAuth is used.

Tools and capabilities

  • Translate text with context, instructions, memories, glossaries, and selectable styles.
  • Detect the language of a single text or an array of texts.
  • List supported language codes.
  • Create, rename, delete, populate, and import translation memories; monitor TMX imports.
  • Create, inspect, rename, delete, populate, import, export, and count glossary entries; monitor CSV imports.

Limitations and notes

The hosted endpoint requires an MCP client that supports the configured HTTP connection and its OAuth flow. Local operation requires Node.js or Docker, depending on the deployment method, plus Lara access credentials. Translation-memory and glossary operations act on resources in the authenticated Lara Translate account. Import operations are asynchronous and expose separate status-checking tools.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Lara MCP

translated/lara-mcp is an MCP server that connects AI clients to the Lara Translate API. Its main tools translate text, detect languages, list supported language codes, and manage translation memories and glossaries, including TMX and CSV imports. It supports hosted OAuth connections and self-hosted stdio deployments with Lara access credentials.

Use the hosted URL `https://mcp.laratranslate.com/v1` for the simplest setup, or run `@translated/lara-mcp@latest` with npx for a local stdio server. Docker and source builds are also supported. Local deployments require Lara access key credentials.

Yes, translated/lara-mcp works with Cursor through its MCP configuration. Add the hosted URL under `mcpServers` in `~/.cursor/mcp.json`, restart Cursor, and authenticate in the browser when a Lara tool is first used.

Use OAuth 2.0 with the hosted endpoint or provide a Lara access key ID and secret for direct authentication. OAuth opens a browser for Lara Translate login, while self-hosted npx and Docker configurations use `LARA_ACCESS_KEY_ID` and `LARA_ACCESS_KEY_SECRET`.

Yes, it can create, rename, delete, and populate both resource types. Translation memories support translation-unit and TMX operations, while glossaries support term entries, CSV import, CSV export, entry counts, and import-status checks.

Related MCP servers

All in Translation Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLara MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/translated-lara-mcp?style=directory)](https://allmcps.com/mcp/translated-lara-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/translated-lara-mcp"><img src="https://allmcps.com/api/badge/translated-lara-mcp?style=directory" alt="Lara MCP on AllMCPs" /></a>