Lara Translate MCP Server
Related Servers
Alternatives to Lara Translate MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server that enables AI agents to interact with Google's Cloud Translation API for translating text between languages.-
- AlicenseAqualityCmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.430 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 gradedqualityCmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.MIT
- AlicenseAqualityBmaintenanceEnables translation, language detection, and language list retrieval via MCP tools, acting as a thin wrapper over a self-hosted LibreTranslate instance.3MIT
TDQS
Scored across 22 tools
Most tools target distinct resources (languages, memories, glossaries, translations, import jobs), and prefixes like list_/create_/update_/delete_ clarify intent. Minor overlap risk between check_import_status and check_glossary_import_status, and between add_translation (a memory unit) and add_glossary_entry, but descriptions distinguish them.
Strong verb_noun snake_case pattern throughout (list_memories, create_glossary, delete_glossary_entry). A few mild deviations: the bare 'translate' verb and 'add_translation' (which operates on memories, not translation) are less self-descriptive than the rest.
22 tools is on the heavier side but justified by three distinct sub-domains (translation, translation memories, glossaries) each needing CRUD plus import/export and async status polling. Each tool earns its place, though it sits near the upper bound of comfortable scope.
Coverage is broad: translation and detection, memory CRUD with translation units and TMX import, glossary CRUD with entries, CSV import/export, and counts. Minor gaps remain (e.g., no explicit list/get for memory translation units or TMX export), but core lifecycle workflows are covered.