Lara MCP: translate one sentence first, via the hosted URL

Who it's for

If you want to attach professional translation to an agent, and you need language detection, contextual translation, a translation memory and a glossary, this service matches. Official text describes it as the MCP server for Lara Translate.

It suits people who can already add a remote server in an MCP client and who hold a Lara Translate login. The official default path is: put only the server URL in the configuration, let the client open a browser to finish login, and do not put an API key in the configuration.

It does not fit people who only want offline translation, or who will not send source text to a remote host. Translation calls leave this machine over the network; source text and terms leave this machine. It also does not fit people who edit the memory store or glossary on the first try: official text writes those capabilities as support items of translate, but the first time you should see whether a translation comes back.

Official repository:

https://github.com/translated/lara-mcp

First try in 3 minutes

There is only one official recommended path: add a remote server named Lara in the client, and use the hosted URL. Do not look for another installer, and do not switch on the first try to a local process that takes access keys.

https://mcp-v2.laratranslate.com/v1

Prerequisites: you can add an MCP server in the client you use, and you can finish browser login. Official text says the client opens a browser; after you log in with Lara Translate credentials you are connected. Submit credentials only in the browser; do not put them in the conversation.

Config location: the server configuration of the current MCP client. Name it Lara, and put the URL above as the address. After you connect, make one low-risk call: use the confirmed translate, and turn one short sentence with no private data into another language. Do not attach unconfirmed function names at the same time. The translation leaves this machine over the network, and there is a privacy boundary.

Success: the client returns one translated sentence, and you did not create a memory-store or glossary entry. If browser login is not finished, first check that this URL was filled as-is; do not change it to another hostname.

Use cases

Case 1: translate one sentence. The object is translate. Official text says it can translate between languages, and supports context, instructions, translation memory, glossary, and the styles faithful, fluid, creative. The first time, pass only short text; do not stack every option at once. Evidence has no parameter table; success is a translation coming back.

Case 2: translation with context. The same tool also writes context and instructions. That is another use: once connected, add context or instructions to the same source text, then translate. Evidence has no field names and no sample sentences; do not invent a memory-store ID or a glossary ID. If the client does not show those options, stop there; do not invent tools that do not appear.

Limits

Official text also writes language detection, translation-memory management and glossary management. Besides translate, this page has no other function names; do not invent detect or list-class names. If a memory store or glossary would be written, the confirmation point is that you have already seen the terms to save, and you accept that they will enter the Lara account, then act.

Official text also has a local start that takes LARA_ACCESS_KEY_ID and LARA_ACCESS_KEY_SECRET. That is not the first-try path, and this page does not give a way to fill those keys. Do not invent unnamed undo, quota or billing. Without a successful login, do not send long text or a customer's source text.