A
licenseA
qualityD
maintenanceEnables MCP-compatible AI applications to translate text through the Lara Translate API, with automatic language detection, context-aware translations, and custom instructions.
1
1,468 npm
MIT
Lara Translate MCP Server
by translated
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.417 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
- AlicenseBqualityDmaintenanceEnables MCP-compatible AI applications to translate text between languages with automatic language detection, contextual hints, custom instructions, and multi-language support.11,468 npmMIT
- AlicenseBqualityDmaintenanceEnables MCP-compatible AI applications to translate text between many languages, with automatic source-language detection, contextual hints, and custom translation instructions.11,468 npmMIT
TDQS
A3.5/5.0
Scored across 22 tools
Disambiguation4/5
Tools are largely organized by resource+action (translation, memory, glossary), so purposes are mostly clear. The only mild overlap is between check_import_status (TMX) and check_glossary_import_status (glossary CSV), and between add_translation and add_glossary_entry, but the descriptions clearly anchor each to its resource.
Naming Consistency4/5
Names follow a consistent snake_case verb_noun pattern (list_*, create_*, delete_*, import_*, export_*). Minor inconsistency in verb choice (get_glossary alongside list_glossaries, add_translation vs create_memory), but the pattern remains predictable.
Tool Count4/5
22 tools is on the high side but justified by three distinct resource domains: translation, translation memories, and glossaries. Each tool maps to a concrete operation with little redundancy, though the set is near the upper bound of comfort.
Completeness4/5
Memory CRUD, glossary CRUD plus entry management, import/export, and async status polling are all covered. Minor gaps remain, such as no way to list or read translation units within a memory (only add/delete) and no memory export, but core workflows are intact.
Maintenance
ActivityActive
ResponsivenessWithin a week