verbaly
Related Servers
Alternatives to verbaly
- AlicenseNot gradedqualityAmaintenanceMcp Server For Doc / Cli / Sdk Integration related to Intlayer i18n solution & CMS868Apache 2.0
- AlicenseBqualityCmaintenanceMCP server for managing translation projects in Weblate. With the ability to search, read and write transltaions.2037 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.59871 npm6MIT
- 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 gradedqualityCmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.121 npm2MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to inspect multi-framework projects, detect hardcoded user-facing strings with AST precision, generate and safely apply internationalization plans, translate and validate catalogs, generate TypeScript types and pseudolocales, format translation files, and audit RTL layout issues.16MIT
- FlicenseNot gradedqualityDmaintenanceEnables translation of JSON i18n files to multiple languages using various AI providers (Google Gemini, OpenAI, Ollama/DeepSeek) with intelligent caching and deduplication.19 npm5-
- AlicenseNot gradedqualityBmaintenanceLets 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.1MIT
- AlicenseAqualityBmaintenanceEnables 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.5MIT
TDQS
Scored across 9 tools
Each tool targets a distinct lifecycle step (init, extract, wrap, translate, write_drafts, missing, drafts, status, doctor), but the read-only reporting trio (status/missing/drafts) and the write side (translate vs write_drafts) sit close together. The descriptions do explicitly delimit them ('for counts use verbaly_status', 'to save translations you wrote yourself, verbaly_write_drafts'), so an agent can separate them, but it takes careful reading.
Every tool uses the same verbaly_<verb/verb_noun> snake_case convention (translate, write_drafts, extract, wrap, init, doctor, missing, drafts, status). The prefix and casing are uniform throughout with no deviations.
Nine tools map cleanly onto the CLI's commands and each earns its place: one per lifecycle stage plus three focused read-only diagnostics. The set is well within the ideal 3-15 range and nothing looks redundant at the command level.
The surface covers setup (init), source handling (extract, wrap), translation generation (translate, write_drafts), and full read-only insight (status, missing, drafts, doctor). The one deliberate gap is approval/review: machine drafts can only be accepted via `verbaly review --approve` outside the tools, which is an intentional human-in-the-loop dead end rather than an oversight.