A
licenseNot graded
qualityA
maintenanceMCP server for translating JSON localization files via DeepL API or local LLMs, enabling agents to estimate, check, and run translations.
MIT
tolgee-mcp
by ytarfa
Related Servers
Alternatives to tolgee-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn 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.15 npm1ISC
- AlicenseNot gradedqualityCmaintenanceMCP server for Localizely that enables managing translation files and projects from any MCP client via natural language.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
- AlicenseNot gradedqualityCmaintenanceOpen-source, self-hosted translation management system with an MCP server that enables AI agents to manage projects, locales, keys, and translations via natural language, and includes a CLI for deterministic file syncing.1MIT
- FlicenseBqualityDmaintenanceAn MCP server for managing Lokalise translations, enabling creation, retrieval, and deletion of translation keys.3-
TDQS
B3.2/5.0
Scored across 27 tools
Disambiguation2/5
Several tools overlap heavily: import_keys and import_translations are nearly identical, and set_translations, create_or_update_translations, and create_key all offer ways to write translations. An agent could easily choose the wrong write operation when the intended behavior is upsert versus update-existing versus bulk import.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern: create_, update_, delete_, list_, get_, set_, import_, export_. The similar names like import_keys and import_translations are confusing semantically, but they do not violate the naming convention.
Tool Count2/5
At 27 tools, the server exceeds the range where each tool clearly earns its place, and some tools appear redundant rather than complementary. Trimming duplicate import/write operations would reduce the surface to a more coherent size.
Completeness4/5
The toolset covers project, language, key, translation, tag, and namespace lifecycle needs, including import/export and translation history. Minor gaps exist such as no explicit translation deletion or tag rename, but agents can work around them with existing operations.
Maintenance
ActivityInactive
ResponsivenessNo issues