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.
      42 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.
      10 npm
      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

    A3.5/5.0

    Scored across 47 tools

    Disambiguation2/5

    Several tools retrieve translation keys with overlapping purposes (get_all_translation_keys, get_all_translation_keys_v2, get_translation_keys, get_translation_key_details), and update_translation_key vs update_translation_key_by_id requires knowing whether to use key or ID. The screenshot-upload trio and auto-translation variants add further boundary confusion, though descriptions do clarify some distinctions.

    Naming Consistency4/5

    Most tools follow the verb_noun snake_case pattern (create_language, delete_tag, get_customers), making the set generally predictable. The main inconsistencies are the v2 suffix and the proliferation of similarly named key/list/detail verbs, but the overall convention remains readable.

    Tool Count2/5

    47 tools is heavy for a single MCP server, even for a broad localization platform. Many could be consolidated (key retrieval variants, screenshot uploads, auto-translation job endpoints), so the count feels inflated rather than earned.

    Completeness4/5

    The tool surface covers the core localization lifecycle: keys, translations, languages, tags, environments, customers, glossary, auto-translation, import/export, and activity. Minor gaps exist—no environment update/delete, no explicit glossary update, no translation deletion separate from keys—but agents can work around most of these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources