add_glossary_entry
Adds or replaces an entry in a glossary in your Lara Translate account. Supports both monodirectional and multidirectional glossaries.
LABSCO SUMMARY
Consistency across documents is the part a general model cannot give you.
A glossary makes a product name or a legal term land the same way every time, and a translation memory means a segment approved once comes back approved rather than re-invented — both applied on the translate call itself rather than in a post-edit. Set-up is the lightest part: the hosted endpoint authenticates through the browser with no key to place, and TMX and CSV imports let existing terminology come across instead of being retyped, though both return an import id you have to poll.
What it is
Translated's Lara Translate as an MCP server, hosted or self-run. Alongside translation it manages the two assets that make professional translation repeatable: translation memories of previously approved segments, and glossaries that pin specific terms.
What you get
- translate takes source and target languages, surrounding context, a style of faithful, fluid or creative, short localization instructions, and the memories and glossaries to apply
- detect_language handles a single string or up to 128 at once, returning the detected language, content type and confidence scores
- list_languages returns the language codes the account supports
- Translation memories created, renamed, listed and deleted, with individual source-target units added and removed — including the sentences before and after, which is what disambiguates a repeated segment
- import_tmx loads an existing TMX file, returning an import id to poll with check_import_status and a progress field to watch
- Glossaries created, renamed, listed, read and deleted, with entries added, replaced and removed in monodirectional or multidirectional form
- import_glossary_csv loads terminology in bulk and polls the same way; export_glossary writes it back out as CSV, and get_glossary_counts reports term and language counts
- no_trace on a translation call, for text that should not be retained
Requirements
A Lara Translate account. The hosted endpoint at https://mcp-v2.laratranslate.com/v1 needs no key at all — the client opens a browser and you log in over OAuth. Running it yourself instead takes an Access Key ID and Secret from the Lara developer console, placed in LARA_ACCESS_KEY_ID and LARA_ACCESS_KEY_SECRET, with npx -y @translated/lara-mcp@latest over stdio or the translatednet/lara-mcp Docker image.
Setup effort
One command — claude mcp add --transport http lara-translate https://mcp-v2.laratranslate.com/v1
USE CASES
01
Translating product copy that must use your terminology
Attach the glossary that pins those terms and pick the style, so brand and industry words come back the way your team writes them.
02
Bringing years of approved translations with you
Import the TMX into a memory, poll until it finishes, then translate with that memory applied.
03
Handling text when you do not know what language it is in
Detect the language first — one string or a batch — then translate into the target with the detection as the source.
04
Keeping a translation improving over time
Add the corrected pairs back into the memory with their surrounding sentences, so the next translation starts from what was approved.
05
Loading terminology your team already maintains in a spreadsheet
Import the CSV into a glossary, poll the job, and check the term and language counts landed as expected.
06
Auditing what terminology is actually in force
List the glossaries, read the one being applied, and export it as CSV for review outside the tool.
22 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_translation
Adds a translation to a translation memory in your Lara Translate account.
check_glossary_import_status
Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_id returned from import_glossary_csv until the import is complete.
check_import_status
Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion.
create_glossary
Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation.
create_memory
Create a translation memory with a custom name in your Lara Translate account. Translation memories store pairs of source and target text segments (translation units) for reuse in future translations.
delete_glossary
Deletes a glossary from your Lara Translate account.
delete_glossary_entry
Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries.
delete_memory
Deletes a translation memory from your Lara Translate account.
delete_translation
Deletes a translation from a translation memory in your Lara Translate account.
detect_language
Detects the language of the provided text. Returns the detected language, content type, and a list of predictions with confidence scores. Accepts a single string or an array of strings (up to 128 elements).
export_glossary
Exports a glossary as CSV from your Lara Translate account. Supports unidirectional and multidirectional formats.
get_glossary
Retrieves a specific glossary by ID from your Lara Translate account. Returns null if the glossary is not found.
get_glossary_counts
Retrieves the term and language counts for a glossary in your Lara Translate account.
import_glossary_csv
Imports a CSV file into a glossary. Supports unidirectional and multidirectional formats. This is an async operation that returns an import job object containing an import_id. Poll with check_glossary_import_status using the returned import_id until the import is complete.
import_tmx
Imports a TMX file into a translation memory. This is an async operation that returns an import job object containing an import_id. Poll with check_import_status using the returned import_id until the import is complete.
list_glossaries
Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation.
list_languages
Lists all supported languages in your Lara Translate account.
list_memories
Lists all translation memories in your Lara Translate account.
translate
Translate text between languages using Lara Translate. Supports language detection, context-aware translations, translation memories, and glossaries. The optional 'instructions' parameter accepts short localization directives (e.g., 'Translate formally') — only provide them when the content specifically requires tone, formality, or terminology adjustments.
update_glossary
Updates the name of a glossary in your Lara Translate account.
update_memory
Updates a translation memory in your Lara Translate account.
BEFORE YOU INSTALL
What to know first
Tools you get
22 tools when we connected. 14 of the 22 create, update, delete or import, and they act on the memories and glossaries in your Lara account.
Requires
A client that can reach a remote MCP server over HTTP
Optional
- LARA_ACCESS_KEY_ID in your environment
- LARA_ACCESS_KEY_SECRET in your environment
CONTEXT COST
Moderate Standing cost
Rated by the size of the 22 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
claude mcp add
TERMINAL
claude mcp add --transport http lara-translate https://mcp-v2.laratranslate.com/v1Hosted endpoint
ENDPOINT URL
https://mcp-v2.laratranslate.com/v1Add this hosted endpoint to your MCP client.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"lara-translate": {
"url": "https://mcp-v2.laratranslate.com/v1"
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"lara-translate": {
"type": "streamableHttp",
"url": "https://mcp-v2.laratranslate.com/v1"
}
}
}Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"lara-translate": {
"type": "http",
"url": "https://mcp-v2.laratranslate.com/v1"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"lara-translate": {
"type": "http",
"url": "https://mcp-v2.laratranslate.com/v1"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"lara-translate": {
"serverUrl": "https://mcp-v2.laratranslate.com/v1"
}
}
}Continue
CONTINUE · JSON
{
"mcpServers": [
{
"name": "lara-translate",
"url": "https://mcp-v2.laratranslate.com/v1"
}
]
}Any MCP client — npx
ANY MCP CLIENT — NPX · 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>"
}
}
}
}Any MCP client — Docker
ANY MCP CLIENT — DOCKER · 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>"
}
}
}
}
