Skip to main content
Glama
Shipi18n

Shipi18n

Official
by Shipi18n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Shipi18n

No user-submitted related servers found.

    Related Servers

    • i18n-keeper

      katerynaKhar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic linting of locale files across JSON, Laravel PHP, gettext, and YAML, with no LLM or network, verifying translations for missing keys, placeholders, plural forms, glossary consistency, and stale entries.
      433 npm
      MIT

    • kaeris-mcp

      RaiGanja
      A
      license
      A
      quality
      B
      maintenance
      AI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.
      7
      MIT

    • @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.
      8 npm
      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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are mostly distinct, but translate_json and translate_file overlap in purpose, and check_locales/diff_locales/review_locales cover related validation concerns that could occasionally be confused.

    Naming Consistency5/5

    All tools follow a clear verb_noun pattern (check_, diff_, review_, translate_, list_), with consistent and descriptive naming throughout.

    Tool Count5/5

    Eight tools is a reasonable, focused set for an i18n workflow, covering validation, diffing, translation, glossary, and language listing without feeling bloated.

    Completeness5/5

    The toolset covers the core i18n lifecycle: listing languages, translating JSON/files, validating structure, checking glossaries, identifying missing keys, and reviewing translation quality. No major gaps are apparent.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources