Skip to main content
Glama
Sign In

localize.dev

by io.github.ufortstephen
OverviewDiscussionsAdmin

Server Details

Find hardcoded UI text, give it translation keys, translate it and write the locale files.

Ownership verified
Status
Healthy
Uptime
45.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
ufortstephen/localize-dev
GitHub Stars
0
ChatGPT
–
Claude
localize-dev

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a reasonably distinct role: `check` is read-only diagnostics, `config` reads settings, `localize` extracts and rewrites code, `translate` only fills locale files, and `add_language` onboards a new locale. The only real overlap is `localize` vs `translate` (both produce translations) and `add_language` vs `translate` (both fill message values), but the descriptions make the code-changing vs locale-only distinction clear.

Naming Consistency3/5

`add_language` follows a verb_noun pattern, while `check`, `config`, `localize`, and `translate` are bare single words, and `config` is a noun rather than an action. The names are readable and short, but the convention is mixed rather than predictable.

Tool Count5/5

Five tools is a tight, well-scoped surface for an i18n workflow: diagnose, read settings, extract, translate, and add a locale. No tool looks redundant or filler; each maps to a distinct step in the pipeline.

Completeness3/5

Core workflow (check → localize/translate → add_language) is covered, but there is no way to remove a language, delete unused translation keys, or write back config changes such as glossary/tone updates — `config` appears read-only despite `add_language` mutating config. These are notable lifecycle gaps that could force agents into manual file editing.

Available Tools

5 tools
add_languageAdd a languageA
Idempotent
Inspect

Adds a language: puts it in targetLocales in localize.config.json (creating the file when missing) and translates every message into it. Needs a localize.dev API key. Send the files in files; nothing is read from or written to your disk. The answer's files are the ones to create or overwrite, each with its whole new content: write them back unchanged.

Inputs: files (required), locale (required), app.

checkCheck localizationA
Read-only
Inspect

Finds UI copy still hardcoded in the code and translations missing or out of date in the locale files, each with its file and line. Changes nothing and needs no API key. Run it before and after localize or translate. Send the files in files; nothing is read from or written to your disk. The answer's files are the ones to create or overwrite, each with its whole new content: write them back unchanged.

Inputs: files (required), app, dir, only, +1 more.

configRead localization settingsA
Read-only
Inspect

The project's localization settings: source and target languages, where locale files live, the folder scanned, the framework and i18n library, and its glossary (terms kept untranslated, preferred translations per language, tone). Read it before writing UI copy or translations by hand, so new strings follow the same conventions. Send the files in files; nothing is read from or written to your disk. The answer's files are the ones to create or overwrite, each with its whole new content: write them back unchanged.

Inputs: files (required), app.

localizeLocalize hardcoded textA
Destructive
Inspect

Extracts hardcoded UI strings into translation keys, rewrites the code to call the i18n library (setting it up when missing), and translates the new messages into every target language. Follows localize.config.json. Needs a localize.dev API key. Send the files in files; nothing is read from or written to your disk. The answer's files are the ones to create or overwrite, each with its whole new content: write them back unchanged.

Inputs: files (required), app, dir, paths, +1 more.

translateFill missing translationsAInspect

Fills in missing translations, and redoes ones whose source text changed, in the existing locale files (JSON, YAML, .po, .arb, strings.xml, .xcstrings, .strings, messages.json). Code is not changed. Needs a localize.dev API key. Send the files in files; nothing is read from or written to your disk. The answer's files are the ones to create or overwrite, each with its whole new content: write them back unchanged.

Inputs: files (required), app, locales.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • Translation Sync MCP Server

      shreyas411
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to keep per-language JSON locale files synchronized with an English source by translating changed keys via MyMemory, validating placeholder tokens, pruning deleted keys, and flagging failures for manual agent translation.
      5
      MIT

    • verbaly

      AronSoto
      A
      license
      A
      quality
      B
      maintenance
      The i18n cycle of a JavaScript project as tools: extract the texts written in code, list missing translations and write machine translations as drafts that a person approves. Works with React, Vue, Svelte, Next.js, Nuxt, SvelteKit and Astro.
      9
      4
      MIT
    Try in Browser
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources