Skip to main content
Glama
ffeldhaus

angular-i18n-mcp

by ffeldhaus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to angular-i18n-mcp

No user-submitted related servers found.

    Related Servers

    • kilo-dev-mcp-server by Kilo-Org

      kilo-dev-mcp-serverofficial

      Kilo-Org
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for internationalization (i18n) tasks, providing tools to translate, move, list, and remove translation keys in JSON files for the Kilo Code extension.
      25
      MIT

    • xliff-processor

      langlink-localization
      A
      license
      C
      quality
      C
      maintenance
      An MCP server for processing XLIFF and TMX translation files, enabling parsing, validation, and manipulation of translation units in localization workflows.
      9
      2
      MIT

    • i18n-mcp

      robin-heat
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing i18n JSON translation files. Provides Claude with structured read/write access to translation files for adding keys, checking coverage, and finding duplicates.
      12
      14 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources