Lingvanex Translate MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINGVANEX_API_KEY | Yes | Your Lingvanex API key for text translation |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translate_textC | Translate text from one language to another |
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 one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as translating text between languages, making it perfectly distinct by default.
The single tool name 'translate_text' follows a clear verb_noun pattern, which is consistent and predictable. Since there is only one tool, naming consistency is inherently perfect.
A single tool is too few for a translation server's apparent scope, which typically involves operations like language detection, batch translation, or language list retrieval. This minimal set feels thin and limits functionality.
The server is severely incomplete for a translation domain, lacking essential operations such as detecting languages, listing supported languages, or handling batch translations. This gap will likely cause agent failures in real-world scenarios.