Skip to content

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

TranslatePress

New in 3.19.0 (Pro). Two dispatcher tools work with TranslatePress (the free edition is enough):

ToolDefaultPurpose
translatepress-readOnThe language setup, every string of a page with its context, string search, theme and plugin strings, progress
translatepress-writeOffWrite and review translations, and add, update, remove or make default the translation language

Enable the write tool under Tools > Plugins > TranslatePress. Only users with TranslatePress’s own translating capability (administrators, unless the site changes it) can read or write strings.

TranslatePress translates the page as it is shown, not a copy of it. Every piece of text on a page is a string in its dictionary, and the same text is one string for the whole site: translating a menu item or the footer once translates it on every page.

  1. Read its strings. get-page-strings with {post_id, lang: "fr_FR"} renders the page in TranslatePress’s preview and returns every string in page order, with the header, menus and footer, plus the theme and plugin text on it. Drafts work too.
  2. Translate whole sentences. TranslatePress splits a sentence at every link or bold word, so “We build fast websites for small teams.” arrives as four strings. Each carries a context with the whole sentence, so the agent can translate it as one sentence and give each fragment its part.
  3. Write them back. translate-strings takes up to 200 translations in one call. Each names the version of the string it read: a string someone else changed in the meantime is a conflict, and nothing is written (force: true writes anyway). One bad entry writes nothing, and dry_run: true checks the whole batch without writing.
  4. Check the page. Open it in the translation language (/fr/...).

Translations are saved as machine translated so a person can review them in TranslatePress’s visual editor. review-strings marks them reviewed, and reviewed: true saves them reviewed straight away. A reviewed translation is never overwritten unless the call passes overwrite_reviewed: true.

search-strings with gettext: true finds text that themes and plugins print, such as “Add to cart”, and translate-strings with gettext: true translates it. get-progress shows how many strings are untranslated, machine translated and reviewed.

Reading a page never starts TranslatePress’s automatic translation, even when an engine is switched on: EMCP’s render blocks it for that one request, and TranslatePress’s own settings stay as they are.

add-language, update-language and set-default-language run TranslatePress’s own settings code. The free edition allows one translation language. Changing the default language and removing a language need confirm: true.

From our test run with the fictional Larkspur Kitchen School, recorded over a real MCP connection with TranslatePress’s free edition. The TranslatePress integration page shows every call the assistant made.

The Larkspur Kitchen School page in Spanish: Cocina con confianza in the hero, menu items Clases, Cursos, Eventos and Reserva una clase, and Spanish class cards.

The page at /es/, served by TranslatePress with the stored translations.

TranslatePress's translation editor in Spanish, with its sidebar on the left and the translated page on the right.

TranslatePress’s own editor opens the same page with the Spanish strings in place.

Every write is recorded in History and can be undone there, except removing a language. An undo of string translations puts every string back in one step, and is refused when any of them changed again since.

Not available in the free edition, and so not through these tools: image alt text, URL slugs, SEO titles and descriptions, more than one translation language, and merging a paragraph into one translation block.