Skip to content

Divi Translator MCP

Translate Divi pages from Claude Desktop. Shortcodes stay intact. HTML structure stays intact. Only the text changes.

Divi Translator MCP is a server that connects to Claude Desktop via the Model Context Protocol. Once installed, you can ask Claude to translate a Divi page — either from a file on disk or directly from a WordPress post — and the server handles everything: extracting translatable text, preserving the Divi shortcode structure, and writing the result back.

The server does not translate anything itself. Claude does the translation. The server extracts the text, keeps track of what must not be changed, and reassembles the final file.

Bulk translation

Extract all translatable text in one call, translate, and submit. One round-trip per document. Recommended for all use cases.

WordPress integration

Connect directly to your WordPress MySQL database. Translate post content, title, slug, and excerpt in one operation. Automatic backup before any change.

Shortcode preservation

Every [et_pb_*] and [/et_pb_*] shortcode is tokenised before extraction and restored exactly after translation. Attributes are never sent to the model.

Chunk markers

Text is split into numbered blocks with {{CHUNK_001}} markers. Claude translates each block. The server matches and reassembles them by number.

Multi-part support

Documents larger than ~30 KB are automatically split into parts. The server asks Claude to translate each part before moving to the next.

Automatic backups

WordPress posts are backed up to disk before any write operation. The backup includes the original title, slug, excerpt, and content.

The server accepts any IETF language code. Common codes used in Divi projects:

CodeLanguageCodeLanguage
enEnglishdeGerman
esSpanishitItalian
frFrenchptPortuguese
nlDutchcaCatalan
  • Claude Desktop (any plan)
  • Go 1.21 or later — only if building from source
  • MySQL access — only for WordPress integration

Current version: 4.3.0 — MCP protocol 2025-11-25 compliant.