A
licenseNot graded
qualityC
maintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.
199 npm
2
MIT
i18n-file-replace-mcp
by cht-codeini
Related Servers
Alternatives to i18n-file-replace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides internationalization MCP tools enabling AI agents to perform translations, locale management, and i18n operations.1,580 npmMIT
- AlicenseAqualityCmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.426 npm1MIT
- AlicenseBqualityDmaintenanceManages Angular internationalization (i18n) by extracting, listing, and updating translation strings in XLIFF format through MCP tools.54 npm1Apache 2.0
- AlicenseAqualityCmaintenanceEnables agents to keep per-language JSON locale files synchronized with an English source by translating changed keys via MyMemory, validating placeholder tokens, pruning deleted keys, and flagging failures for manual agent translation.5MIT
- AlicenseAqualityDmaintenanceEnables automatic discovery and fast searching of translation files in projects, supporting partial/exact key-value matching with file watching and multiple translation file formats.2MIT
TDQS
A4.2/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct resource/action: replace vs preview, profile management (list/get/save), and resource queries (projects/sets/keys/download). Descriptions clearly distinguish overlapping operations like replace_file and preview_replace.
Naming Consistency5/5
All tool names follow the same lower_snake_case convention with an action-first pattern (replace_, preview_, list_, get_, save_, download_). The naming is uniform and predictable across the entire set.
Tool Count5/5
9 tools are well-scoped for the purpose of i18n file replacement and associated profile/resource management. The count is comfortably within the ideal 3-15 range, and each tool earns its place.
Completeness4/5
Core workflows (preview, replace, profile create/update, and resource browsing/export) are fully covered. A minor gap is the absence of a profile deletion tool, leaving the profile lifecycle slightly incomplete, but agents can still work around this easily.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues