Skip to main content
Glama
hepter

i18n-codelens-mcp

by hepter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to i18n-codelens-mcp

No user-submitted related servers found.

    Related Servers

    • @mcpx-digital/i18n-keys

      TheoryofShadows
      A
      license
      A
      quality
      C
      maintenance
      Enables comparing local JSON/YAML locale files to find missing or extra keys against a base locale, detect empty, null, or whitespace translations, and list flattened dot-path keys for a single file. Works entirely on local files with no network calls or translation APIs.
      3
      MIT

    • i18n Agent

      kwunlokng
      A
      license
      Not graded
      quality
      D
      maintenance
      AI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.
      19 npm
      MIT

    • JSON Editor MCP

      peternagy1332
      A
      license
      A
      quality
      D
      maintenance
      Enables efficient JSON file editing with targeted read, write, delete, and deep merge operations using dot notation paths, optimized for managing multilingual projects and large configuration files.
      4
      12 npm
      1
      MIT

    • 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.
      6 npm
      1
      ISC
    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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists between i18n_get_translations and i18n_search_keys (both retrieve translation values) and between i18n_key_references and i18n_file_keys (both report code references). Descriptions help clarify the intended use, but an agent might still misselect for tasks like finding missing translations.

    Naming Consistency3/5

    All names share the i18n_ prefix and snake_case, but the verb/noun structure is mixed: some are noun phrases (i18n_key_references, i18n_project_info, i18n_file_keys, i18n_audit) and others are verb_noun (i18n_get_translations, i18n_search_keys, i18n_upsert_translations). This deviation from a uniform verb_noun pattern makes it only moderately consistent.

    Tool Count5/5

    With 10 tools, the set is well-scoped for an i18n code lens server. Each tool covers a distinct operation (references, info, get, search, file keys, audit, upsert, delete, rename, format) without obvious redundancy, and the count sits comfortably in the recommended 3–15 range.

    Completeness4/5

    The surface covers the core i18n key lifecycle: create/update (upsert), read (get/search), delete, rename, format, audit, and code references. Minor gaps exist, such as no explicit tool to list all keys or manage locales, but these can be worked around with search or project info.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources