texterify-mcp

Search and list translation keys (i18n string identifiers) in the configured Texterify project. Returns keys with their current translations, tags, and pagination metadata. Use this to find key IDs needed by get_key, update_key, delete_keys, and set_translation. The response includes: data (array of keys with name, description, html_enabled, pluralization_enabled), included (translations with content per language, tags), and meta.total (total count for pagination). Search matches against key name, description, and translation content (case-insensitive).

Retrieve a single translation key with all its translations across every project language, plus related tags and placeholders. Use this to inspect the complete translation state of a specific key before updating or to verify translations after setting them. The response includes: data (the key with name, description, html_enabled, pluralization_enabled), included (all translations with their content and language info, tags, placeholders). Requires a key_id — use list_keys to find it.

Create a new translation key (i18n string identifier) in the configured Texterify project. This only creates the key entry — it does NOT add any translated content. After creating a key, call set_translation for each language to add translations. Key names must be unique within the project; duplicate names return a validation error with code "TAKEN". Typical workflow: create_key -> list_languages -> set_translation for each language.

Update an existing translation key's metadata: name, description, or HTML/pluralization settings. Only the fields you provide are changed — omitted fields stay as-is. Important: this does NOT modify translations. Use set_translation to change translated content. Returns { "message": "Key updated" } on success (not the full key object — call get_key afterward if you need the updated key data).

Permanently delete one or more translation keys and ALL their associated translations from the configured Texterify project. This action is irreversible — the keys, all their translations across every language, and any tag associations are destroyed. Returns { "message": "Keys deleted" } on success. Use list_keys first to verify which keys you are deleting.

Set the translated text for a specific key in a specific language (upsert). If a translation already exists for the key+language pair it is updated; otherwise a new translation is created. Requires both a key_id (from list_keys, get_key, or create_key) and a language_id (from list_languages). For keys with pluralization_enabled, provide plural forms alongside the main content — which forms to use depends on the target language's CLDR plural rules (check the language's supports_plural_* flags from list_languages). Typical workflow: list_languages to get language_id -> set_translation for each language.

Create a new translation key and set translations for multiple languages in a single operation. Accepts language codes (e.g., 'en', 'de', 'fr') instead of language IDs — the tool resolves codes to IDs internally by fetching the project's configured languages. If the key is created but any translation fails, the key is automatically rolled back (deleted). This combines create_key + multiple set_translation calls into one atomic-like operation.

List languages configured in the Texterify project. Use this to get language IDs required by set_translation and to check translation progress per language. The response includes: data (languages with name, is_default flag, progress as 0-100 percentage of translated keys, and supports_plural_* flags indicating which CLDR plural forms apply), included (country_code and language_code with their codes), and meta.total. The language marked is_default is the primary language of the project.

List all Texterify projects accessible to the authenticated user. Use this to discover project IDs and names, or to verify the currently configured project. Note: all other tools already operate on the pre-configured project (set via TEXTERIFY_PROJECT_ID environment variable), so this tool is mainly useful for discovery and verification. The response includes: data (projects with name, description, word_count, character_count, organization_id) and meta.total.