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. | |
| LARA_ACCESS_KEY_SECRET | Yes | Your Lara 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
With only a single tool, there is no possibility of confusing it with another operation. The tool's purpose is unambiguous: translate text between languages.
The lone name 'translate' is a clear, conventional verb that matches the server's single responsibility. There is no mixed convention to worry about.
One tool is on the thin side for a translation service, which commonly exposes related operations like language listing or batch translation. Still, the surface is focused and not bloated.
Translation itself is covered, including detection and context, but there are notable gaps: no way to list supported languages, no separate detection endpoint, and no batch or glossary management. Agents can still accomplish the core task but may hit dead ends for discovery.