Skip to main content
Glama
simplelocalize

SimpleLocalize MCP Server

Official
by simplelocalize
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SimpleLocalize MCP Server

No user-submitted related servers found.

    Related Servers

    • tolgee-mcp

      ytarfa
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that wraps the Tolgee localization platform API, enabling LLMs to manage translation projects, keys, translations, languages, and related workflows.
      27
      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.
      6 npm
      1
      ISC

    • 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

    A3.6/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools target distinct resources (keys, translations, languages, customers, environments, glossary, jobs, activity), but there is notable overlap among key retrieval tools (get_translations, get_all_translation_keys, get_translation_keys, get_all_translation_keys_v2, get_translation_key_details) and screenshot upload variants, which could cause misselection without careful reading.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (get_, create_, update_, delete_, import_, export_, publish_, etc.) with clear resource nouns. Minor deviations include versioned tool names like get_all_translation_keys_v2 and the slight ambiguity between singular/plural job tools, but overall the pattern is predictable.

    Tool Count2/5

    47 tools is excessive for most MCP servers, even for a comprehensive translation management platform. While each tool addresses a specific operation, the sheer number overwhelms agents and suggests possible consolidation (e.g., merging single/bulk variants or combining related getters). The count is well above the typical 3-15 range.

    Completeness4/5

    The tool surface is quite complete, covering CRUD for translation keys, translations, languages, tags, customers, glossary entries, environments, and auto-translation jobs, plus import/export and activity tracking. Minor gaps include missing update/delete for environments and no dedicated single-translation getter, but these are workable limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources