Lara Translate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LARA_ACCESS_KEY_ID | Yes | Your Lara API access key ID obtained from Lara Translate account | |
| LARA_ACCESS_KEY_SECRET | Yes | Your Lara API access key secret obtained from Lara Translate account |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translateA | 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. IMPORTANT: 'target' accepts exactly one language code per call. If the user asks to translate into multiple languages (e.g., 'into Italian and German'), call this tool once per target language and present all resulting translations together. IMPORTANT: 'glossaries' requires glossary IDs in the 'gls_*' format, not glossary names. If the user refers to a glossary by name (e.g., 'our company glossary', 'the marketing glossary'), call list_glossaries first, match the name, and use the returned ID here. If no matching glossary is found, tell the user instead of guessing an ID. |
| detect_languageA | 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). Use this tool explicitly whenever the user asks to know or confirm what language a text is written in — including when that request is combined with a translation request (e.g., 'detect the language of this text and translate it into English'). In that case, call this tool first, tell the user which language was detected, and only then call the translate tool (you do not need to pass the detected language as 'source' to translate — translate can auto-detect on its own — but the user still expects to be told the result of detection). |
| list_languagesA | Lists all supported languages in your Lara Translate account. |
| list_memoriesA | Lists all translation memories in your Lara Translate account. |
| create_memoryB | 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. |
| update_memoryC | Updates a translation memory in your Lara Translate account. |
| delete_memoryC | Deletes a translation memory from your Lara Translate account. |
| add_translationC | Adds a translation to a translation memory in your Lara Translate account. |
| delete_translationB | Deletes a translation from a translation memory in your Lara Translate account. |
| import_tmxA | 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. |
| check_import_statusA | 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. |
| list_glossariesA | Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation. |
| get_glossaryA | Retrieves a specific glossary by ID from your Lara Translate account. Returns null if the glossary is not found. |
| create_glossaryA | Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation. |
| update_glossaryB | Updates the name of a glossary in your Lara Translate account. |
| delete_glossaryC | Deletes a glossary from your Lara Translate account. |
| add_glossary_entryA | Adds or replaces an entry in a glossary in your Lara Translate account. Supports both monodirectional and multidirectional glossaries. |
| delete_glossary_entryA | Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries. |
| import_glossary_csvA | 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. |
| check_glossary_import_statusA | 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. |
| export_glossaryB | Exports a glossary as CSV from your Lara Translate account. Supports unidirectional and multidirectional formats. |
| get_glossary_countsA | Retrieves the term and language counts for a glossary in your Lara Translate account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Translation Memories | List of translation memories in your Lara Translate account. |
| Supported Languages | List of Lara Translate supported languages. |
TDQS
Scored across 22 tools
Tools are largely organized by resource+action (translation, memory, glossary), so purposes are mostly clear. The only mild overlap is between check_import_status (TMX) and check_glossary_import_status (glossary CSV), and between add_translation and add_glossary_entry, but the descriptions clearly anchor each to its resource.
Names follow a consistent snake_case verb_noun pattern (list_*, create_*, delete_*, import_*, export_*). Minor inconsistency in verb choice (get_glossary alongside list_glossaries, add_translation vs create_memory), but the pattern remains predictable.
22 tools is on the high side but justified by three distinct resource domains: translation, translation memories, and glossaries. Each tool maps to a concrete operation with little redundancy, though the set is near the upper bound of comfort.
Memory CRUD, glossary CRUD plus entry management, import/export, and async status polling are all covered. Minor gaps remain, such as no way to list or read translation units within a memory (only add/delete) and no memory export, but core workflows are intact.