xliff-processor
Related Servers
Alternatives to xliff-processor
No user-submitted related servers found.
Related Servers
- 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 Localizely that enables managing translation files and projects from any MCP client via natural language.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.MIT

kilo-dev-mcp-serverofficial
AlicenseNot gradedqualityFmaintenanceAn MCP server for internationalization (i18n) tasks, providing tools to translate, move, list, and remove translation keys in JSON files for the Kilo Code extension.24MIT- AlicenseAqualityBmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.410 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for managing translation projects in Weblate. With the ability to search, read and write transltaions.2068 npm23MIT
TDQS
Scored across 9 tools
Each tool targets a distinct action (export, process, validate, replace, get info) with specific file types (XLIFF or TMX). The only potential overlap is process_xliff and process_xliff_with_tags, but the latter explicitly handles tags, making them clearly distinguishable.
All tools follow a consistent verb_noun pattern in snake_case, e.g., export_tmx_file, process_xliff, validate_tmx. The naming is predictable and uniform across the entire set.
With 9 tools covering export, process, validate, replace, and server info for both XLIFF and TMX, the count is well-scoped for a file processing server. No tools feel extraneous or missing.
The tool surface covers the core lifecycle for XLIFF and TMX: export, process, validate, and replace. Minor gaps exist, such as missing import or merge tools, but for a focused XLIFF processor, it is largely complete.