Translation MCP Server
Related Servers
Alternatives to Translation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for managing translation projects in Weblate. With the ability to search, read and write transltaions.20215 npm22MIT
- FlicenseNot gradedqualityDmaintenanceA ModelContextProtocol server providing high-quality translation services with a three-stage translation workflow (analysis, segmented translation, full-text review) that supports multiple languages and integrates with Claude and OpenAI-compatible models.26-
- AlicenseNot gradedqualityDmaintenanceServer for managing academic literature with structured note-taking and organization, designed for seamless interaction with Claude. Built with SQLite for simplicity and portability.19MIT
- FlicenseAqualityDmaintenanceThe server facilitates natural language interactions for exploring and understanding codebases, providing insights into data models and system architecture using a cost-effective, simple setup with support for existing Claude Pro subscriptions.427-
- AlicenseAqualityBmaintenanceA server that enables vector and keyword search capabilities in Typesense databases through the Model Context Protocol, providing tools for collection management, document operations, and search functionality.1410MIT
- AlicenseNot gradedqualityDmaintenanceThis server provides database access capabilities to Claude, supporting SQLite, SQL Server, PostgreSQL, and MySQL databases.693 npmMIT
TDQS
Scored across 8 tools
Each tool has a distinct purpose with clear boundaries: analyze context, find missing translations, get configuration, save translations, set configuration, translate a key, translate a namespace, and validate translations. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'analyze_translation_context', 'find_missing_translations', and 'save_translations'. This predictability aids in understanding and usage without any deviations or mixed conventions.
With 8 tools, the server is well-scoped for translation management, covering configuration, translation operations, validation, and analysis. Each tool serves a specific role, avoiding bloat or thinness, making the count appropriate for the domain.
The tool set provides comprehensive coverage for translation workflows: configuration management (get/set), translation operations (key/namespace), saving, validation, and analysis for missing translations and context. There are no obvious gaps, supporting full CRUD-like lifecycle handling.