A
licenseNot graded
qualityA
maintenanceProvides internationalization MCP tools enabling AI agents to perform translations, locale management, and i18n operations.
746 npm
MIT
angular-i18n-mcp
by ffeldhaus
Related Servers
Alternatives to angular-i18n-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to replace hardcoded text in source files with i18n resource keys, with support for previewing changes, profiles, resource sets, and machine translation.910 npmMIT
- AlicenseAqualityCmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.430 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.72 npm2MIT
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- AlicenseCqualityCmaintenanceAn MCP server for processing XLIFF and TMX translation files, enabling parsing, validation, and manipulation of translation units in localization workflows.92MIT
TDQS
B3.2/5.0
Scored across 5 tools
Disambiguation4/5
Most tools target distinct operations (config read, extraction, update), but list_new_translations and list_all_translations are close cousins that an agent could conflate. Descriptions clarify the difference (state='initial' vs all units), keeping ambiguity low.
Naming Consistency5/5
All names use a consistent snake_case verb_noun pattern (get_i18n_settings, extract_i18n, list_new_translations, list_all_translations, update_translations). The convention is predictable throughout.
Tool Count5/5
Five tools is well-scoped for an Angular i18n workflow, covering config, extraction, listing, and updating without redundancy. Each tool clearly earns its place.
Completeness4/5
The core lifecycle (read settings, extract, list untranslated/all, update) is covered. Minor gaps exist, such as reading a single unit or compiling/validating translations, but these are largely handled by the underlying Angular CLI.
Maintenance
ActivityInactive
ResponsivenessNo issues