F
licenseNot graded
qualityD
maintenanceAn MCP (Multi-Agent Conversation Protocol) Server that enables AI agents to interact with Google's Cloud Translation API for translating text between languages.
-
Lara Translate MCP Server
by translated
Related Servers
Alternatives to Lara Translate MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.440 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides standardized translation services across six languages (Arabic, Chinese, English, French, Russian, Spanish) using Claude Sonnet 3.5, with support for different domains and formality levels.3MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for translation and localization workflows. It exposes tools for glossary lookup, translation memory reuse, segment alignment, and demo multicloud translation.-
- AlicenseNot gradedqualityAmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.MIT
- AlicenseAqualityAmaintenanceAn MCP server providing automated workflows, rules, and actionable tools for implementing full multilingual localization in Laravel applications.12MIT
TDQS
A3.6/5.0
Scored across 22 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessUnresponsive