Skip to main content
Glama
Sign In
the-i18n-mcp

the-i18n-mcp

by fabkho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to the-i18n-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-locator

      Tankonyako
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets AI agents read and write locale JSON translation files directly from the conversation without loading the whole catalog into context.
      15 npm
      1
      ISC

    • i18n-mcp

      skk2010
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for managing Rails-style localization files (YAML/JSON), enabling coding agents to read, search, write, and audit translations without hand-editing files.
      7
      8 npm
      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
      16 npm
      1
      MIT

    • texterify-mcp

      mogharsallah
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides LLM agents with full access to the Texterify translation management API. It enables users to search, create, update, and delete translation keys and their values directly through natural language within their development environment.
      23 npm
      1
      ISC
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct i18n operation: discovery, listing, reading, writing, removing, moving, translating, scaffolding, and four different key-health checks. The only mild overlap is get_translations vs search_translations, but their descriptions clearly separate exact/prefix retrieval from value-based search. No two tools appear to do the same thing.

    Naming Consistency4/5

    The set is predominantly verb_noun snake_case (list_namespaces, get_translations, write_translations, find_undefined_keys). Minor deviations: 'discover' is a bare verb, and pluralization varies (translations vs translation_key/status). The verb-led convention is still clear and predictable overall.

    Tool Count5/5

    15 tools is well within the ideal 3-15 range and each one maps to a distinct operation in translation management. The set feels purpose-built rather than padded or thin.

    Completeness5/5

    Covers the full lifecycle: discover, list/search/get, write/remove, move/rename, translate, scaffold, and comprehensive health checks (missing, undefined, orphan, duplicate, status). No obvious dead ends for the stated i18n management purpose; framework config edits are intentionally left out.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources