angular-i18n-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCALE_DIR | No | The directory where translation files are stored. Defaults to src/locale. | src/locale |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_i18nB | Extract i18n strings and merge into target files using Angular CLI |
| list_new_translationsC | List new (untranslated) units with state='initial' |
| list_all_translationsC | List all units in the translation file |
| update_translationsC | Update multiple translations in a single file (max 50) |
| get_i18n_settingsB | Get i18n settings from angular.json |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
Five tools is well-scoped for an Angular i18n workflow, covering config, extraction, listing, and updating without redundancy. Each tool clearly earns its place.
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.