SimpleLocalize MCP Server
Related Servers
Alternatives to SimpleLocalize MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Phrase Strings to manage translation projects, keys, and translations. Enables AI assistants to perform CRUD operations on projects, locales, and translations programmatically.-
- AlicenseBqualityDmaintenanceAn MCP server that enables users to add translation keys to Lokalise projects using natural language through Cursor or standalone interfaces. It allows for the specification of project names, translation keys, default values, and target platforms.13 npm4ISC
- AlicenseNot gradedqualityCmaintenanceMCP server for Localizely that enables managing translation files and projects from any MCP client via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides DeepL translation capabilities, allowing AI assistants to translate text between supported languages via the DeepL API.952 npm3MIT
- 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
- AlicenseAqualityFmaintenanceA Model Context Protocol server for reading, writing, and managing GNU Gettext .po translation files, enabling language models to perform file operations, entry management, partial updates, and fuzzy entry detection.4MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: create keys, duplicate translations, get environment status, get missing translations, get translations for keys, publish translations, and update translations. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with clear, descriptive names: create_translation_keys, duplicate_translation, get_environment_status, get_missing_translations, get_translations_for_keys, publish_translations, update_translations. The naming is uniform and predictable throughout.
With 7 tools, this server is well-scoped for a localization/translation management system. Each tool serves a specific, necessary function in the domain, covering key operations without bloat or redundancy.
The toolset covers core translation management workflows well: creation, duplication, retrieval (with various filters), updating, and publishing. A minor gap is the lack of explicit delete operations for keys or translations, which agents might need to work around, but overall coverage is strong.