nativ-mcp
OfficialRelated Servers
Alternatives to nativ-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.165 npm2MIT
- AlicenseNot gradedqualityBmaintenanceAI-powered translation MCP server with EU AI Act compliance, enabling automated translation workflows via the MCP protocol.6 npm56 PyPIMIT
- AlicenseAqualityBmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.440 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for translation and localization workflows. It exposes tools for glossary lookup, translation memory reuse, segment alignment, and demo multicloud translation.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive localization data for 174 locales, enabling AI agents to generate culturally-adapted multilingual content.MIT
- AlicenseNot gradedqualityDmaintenanceAI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.8 npmMIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose within the localization domain: add_translation_memory_entry stores translations, get_brand_voice retrieves brand guidelines, get_languages and get_style_guides fetch configuration, get_translation_memory_stats provides metrics, search_translation_memory finds existing translations, translate handles single translations, and translate_batch processes multiple texts. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun naming pattern (e.g., add_translation_memory_entry, get_brand_voice, search_translation_memory). The verbs are descriptive and appropriate for each action (add, get, search, translate), and snake_case is used uniformly throughout, creating a predictable and readable naming convention.
With 8 tools, the server is well-scoped for localization tasks, covering core operations like translation, memory management, and configuration retrieval. Each tool serves a specific and necessary function without redundancy, making the count appropriate for the domain and avoiding both bloat and insufficiency.
The tool set provides comprehensive coverage for AI-driven localization, including translation (single and batch), translation memory management (add, search, stats), and configuration access (brand voice, languages, style guides). A minor gap exists in the lack of update or delete operations for translation memory entries or style guides, but agents can still perform essential workflows effectively.