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 confusing it with another operation. Its purpose is clearly translation.
The single tool name 'translate' is a clear verb that directly reflects its action. With only one tool, there are no naming convention conflicts.
The server exposes only one tool, which is thin even for a narrowly scoped translation service. It covers the core action but leaves no room for related operations such as language listing or batch translation.
The translate tool covers the primary translation workflow and mentions language detection and context awareness. However, there are notable gaps such as listing supported languages, batch translation, or separate detection operations.