Skip to main content
Glama

Related Servers

Alternatives to verbaly

  • A
    license
    B
    quality
    C
    maintenance
    MCP server for managing translation projects in Weblate. With the ability to search, read and write transltaions.
    20
    37 npm
    24
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    An MCP server that wraps the Tolgee localization platform API, enabling LLMs to manage translation projects, keys, translations, languages, and related workflows.
    27
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables 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

  • A
    license
    A
    quality
    B
    maintenance
    Enables 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.
    16
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Lets 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.
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables 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.
    5
    MIT

TDQS

A4.3/5.0

Scored across 9 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessNo recent community issues