verbaly
Related Servers
Alternatives to verbaly
- AlicenseNot gradedqualityAmaintenanceMcp Server For Doc / Cli / Sdk Integration related to Intlayer i18n solution & CMS856Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for managing translation projects in Weblate. With the ability to search, read and write transltaions.2063 npm24MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to Lokalise translation management platform with 59 tools across 11 domains, enabling localization teams to manage projects, translations, tasks, and workflows through natural conversation.59451 npm5MIT
- AlicenseBqualityDmaintenanceAn MCP server that wraps the Tolgee localization platform API, enabling LLMs to manage translation projects, keys, translations, languages, and related workflows.27MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-aware clients to manage inlang i18n catalogs, including discovering projects, parsing catalogs, handling keys, locales, variants, plurals, validating translations, and compiling messages, without parsing catalog files themselves.-
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables localization of React, Next.js, and Vue apps from an AI assistant by managing projects, languages, translations, glossaries, style guides, and GitHub repository integration.MIT
- AlicenseNot gradedqualityBmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.125 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables translation of JSON i18n files to multiple languages using various AI providers (Google Gemini, OpenAI, Ollama/DeepSeek) with intelligent caching and deduplication.20 npm5-
- AlicenseNot gradedqualityAmaintenanceLets a coding agent find, translate, validate and review an app's existing localization files (Android strings.xml, Apple String Catalogs, gettext) directly in the repo, supplying code usage, comments, glossary and voice notes as context. Placeholders, plural forms, escaping and markup are checked in code before any translation is written, and results land as reviewable drafts that never overwrite hand edits or approved work.72 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents, developers, and CI pipelines to run deterministic, offline localization QA — pseudolocalization, locale linting for separators/dates/placeholders/RTL, and glossary enforcement across 20 locales — without any network access or API key. When an OpenAI-compatible endpoint is configured, it can also translate into multiple locales and lint the results, or otherwise emit structured translation jobs instead of fabricating translations.3 npmMIT
- AlicenseAqualityBmaintenanceAI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.7760 PyPIMIT
TDQS
Scored across 9 tools
Each tool maps to a distinct CLI operation (init, doctor, wrap, extract, status, missing, translate, write_drafts, drafts) with clear boundaries, and the descriptions explicitly orient the agent (doctor first, init when doctor says no config). The one soft spot is drafts: pending-review listings are surfaced in verbaly_status, optionally in verbaly_missing, and again in verbaly_drafts, so an agent may pick the wrong one for that question.
Every tool uses the same verbaly_ snake_case prefix with a single short token, which is highly predictable and mirrors the CLI commands. Minor deviation: the tokens mix verbs (init, wrap, extract, translate) with nouns/adjectives (status, missing, doctor, drafts), so the suffix does not consistently signal an action.
Nine tools is well within the ideal 3-15 range and each corresponds to a real stage of the localization workflow with no filler. Nothing appears redundant by count alone.
The surface covers onboarding (init, wrap), maintenance (extract, translate, write_drafts), and inspection (doctor, status, missing, drafts), with read/write variants and dryRun/overwrite flags. Gaps are minor: approving drafts and locale management are deliberately excluded (human-only), and pruning exists only as an extract flag rather than a standalone operation.