Skip to main content
Glama
skk2010

i18n-mcp

by skk2010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 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.
      7 npm
      1
      ISC

    • the-i18n-mcp

      fabkho
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.
      15
      251 npm
      11
      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
      2 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.
      4 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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: listing locales, listing keys, fetching a specific key, searching, setting, deleting, and auditing. No two tools appear to do the same thing.

    Naming Consistency5/5

    Tool names follow a consistent, predictable pattern: plural nouns for listing actions (keys, locales), and verb_noun for operations (get_key, set_key, delete_key). The one outlier, 'missing', is still clear as an audit verb.

    Tool Count5/5

    Seven tools is a well-scoped count for an i18n management server, covering the essential operations without bloat.

    Completeness5/5

    The toolset provides full lifecycle coverage for translation keys: read (keys, get_key, search), write (set_key), delete (delete_key), and audit (missing, locales). Minor operations like rename/move are possible via set+delete, so no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources