@langapi/mcp-server
Related Servers
Alternatives to @langapi/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Localizely that enables managing translation files and projects from any MCP client via natural language.MIT
- AlicenseAqualityDmaintenanceMCP server for page-level i18n translation using Alibaba Cloud Qwen models, supporting incremental translation, glossary, and multiple target languages.33 npmMIT
- AlicenseNot gradedqualityBmaintenanceAI-powered translation MCP server with EU AI Act compliance, enabling automated translation workflows via the MCP protocol.8 npm55 PyPIMIT
- AlicenseAqualityBmaintenanceMCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.15251 npm11MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI agents read and write locale JSON translation files directly from the conversation without loading the whole catalog into context.8 npm1ISC
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: scanning locales, comparing translation status, syncing translations, and checking account info. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (list_, get_, sync_, get_). The naming is uniform and predictable.
Four tools are well-scoped for a translation management server. Each tool covers a necessary step in the workflow without redundancy, and the count is within the ideal range.
The tool set covers the core lifecycle: discovering locales, checking status, syncing, and account monitoring. Minor gaps like translation history or manual key editing are absent, but these are not essential for the main workflow.