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 |
|---|---|
| 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). |
| 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. |
| 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. |
| delete_memoryB | Deletes a translation memory from your Lara Translate account. |
| update_memoryB | Updates a translation memory in your Lara Translate account. |
| add_translationB | Adds a translation to a translation memory in your Lara Translate account. |
| delete_translationA | 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_memoriesA | Lists all translation memories in your Lara Translate account. |
| list_languagesA | Lists all supported languages in your Lara Translate account. |
| 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_glossaryB | 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_glossaryA | Deletes a glossary from your Lara Translate account. |
| 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_glossaryA | 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. |
| 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. |
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
Most tools are clearly separated by resource (memory vs glossary vs translation vs language detection), but add_translation/delete_translation and add_glossary_entry/delete_glossary_entry could be confused with the main translate tool at a glance. The descriptions clarify the distinction, so only minor ambiguity exists.
The naming follows a consistent verb_noun pattern (detect_language, create_memory, delete_memory, import_tmx, check_import_status). Minor deviations exist: get_glossary_counts and add_glossary_entry use a different noun grouping than list_glossaries/get_glossary, but the pattern is still predictable.
22 tools is on the higher end but appropriate for a translation platform covering translation, memories, glossaries, and imports. Each tool maps to a distinct operation, though the count is slightly heavy for the apparent scope.
The surface covers the core lifecycle for translation memories (create/list/update/delete, add/delete translations, import) and glossaries (create/get/list/update/delete, import/export, entry management). Minor gaps include no update_translation or update_glossary_entry, but agents can work around these by replacing entries.