A
licenseB
qualityD
maintenanceAn 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
by mogharsallah
Related Servers
Alternatives to texterify-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.MIT
- AlicenseAqualityBmaintenanceAn MCP server for managing Rails-style localization files (YAML/JSON), enabling coding agents to read, search, write, and audit translations without hand-editing files.710 npmMIT
- AlicenseAqualityBmaintenanceMCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.15251 npm11MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Localizely that enables managing translation files and projects from any MCP client via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceAn 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 npm1ISC
TDQS
A4.3/5.0
Scored across 7 tools
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between create_key and create_key_with_translations, as both create keys with slightly different workflows. The descriptions clarify that one is atomic with translations while the other is just the key, but an agent might still be confused about which to use initially. Other tools like list_keys, get_key, and update_key are clearly differentiated.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., create_key, list_keys, update_key), with clear and predictable naming. There are no deviations in style or convention, making it easy for an agent to understand the action and target resource at a glance.
Tool Count5/5
With 7 tools, this server is well-scoped for managing translation keys and projects in Texterify. It covers core operations like creation, retrieval, listing, and updates, without being overly complex or too sparse. The count aligns well with the domain's typical needs for i18n workflows.
Completeness3/5
The toolset covers key creation, retrieval, listing, and updates, but there are notable gaps: it lacks a delete_key tool for removing keys and a set_translation tool for updating translations individually (only available via create_key_with_translations). This forces agents into specific workflows and may cause failures when trying to modify translations without creating new keys.
Maintenance
ActivityInactive
ResponsivenessNo issues