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 Translate API access key ID. | |
| LARA_ACCESS_KEY_SECRET | Yes | Your Lara Translate API access key secret. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translateB | Translate text between languages with support for language detection and context-aware translations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly distinct and self-contained.
The single tool name 'translate' follows a clear verb-style convention. With only one tool, consistency is trivially satisfied.
A single translation tool is focused but feels thin for an MCP server. Basic translation is covered, but related operations like batch translation or language listing are not exposed as separate tools.
The core translation operation is present, including language detection and context-aware translation. However, the surface lacks common supporting operations such as batch translation, listing supported languages, or document/file translation.