Skip to main content
Glama
Sign In
Localizable XStrings MCP Server

Localizable XStrings MCP Server

by iamnotagentleman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Localizable XStrings MCP Server

No user-submitted related servers found.

    Related Servers

    • locli

      mariohahn
      A
      license
      Not graded
      quality
      B
      maintenance
      Localization backend for coding agents: push iOS String Catalogs, Android strings.xml and ICU JSON to locli, translate with the project's tone, glossary and UI context, and pull only human-approved releases.
      MIT

    • kaeris-mcp

      kaeris-io
      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
      788 PyPI
      MIT

    • Xcode MCP Server

      ebowwa
      A
      license
      B
      quality
      D
      maintenance
      Provides programmatic access to Xcode functionality, enabling AI assistants to create, build, test, and manage iOS/macOS projects directly.
      33
      10 npm
      5
      MIT
    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

    B3.3/5.0

    Scored across 7 tools

    Disambiguation3/5

    There is significant overlap between translate_tool, apply_tool, and translate_key_tool, as all involve translating strings, which could confuse an agent. However, apply_missing_tool is distinct by focusing only on missing translations, and get_* tools are clearly separate for retrieval purposes.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., get_keys_tool, translate_key_tool), but apply_missing_tool and apply_tool deviate slightly by omitting the noun, which is a minor inconsistency. Overall, the naming is readable and predictable.

    Tool Count5/5

    With 7 tools, the count is well-scoped for managing xcstrings files, covering retrieval, translation, and application operations. Each tool serves a distinct role in the localization workflow, making the set appropriately sized.

    Completeness4/5

    The toolset covers key aspects like retrieving base strings, keys, and languages, plus translation and application functions. A minor gap is the lack of tools for updating or deleting translations, but core operations are present, allowing agents to handle most localization tasks.

    Resources