Problem/Motivation

There is currently no MCP tool coverage for content translation workflows. Concretely useful for editors driving Drupal through MCP clients:

  • a tool that lists the translatable fields of an entity with their current source values, and
  • a tool that creates/updates a translation of a node including its paragraph tree, keeping the translated paragraph entities linked to the same revisions/deltas as the source.

Proposed resolution

We built this as an mcp_tools_translate submodule (two tools: read translatable content, create linked node/paragraph translations) and currently ship it as a composer patch on 1.0.0-beta14 - an arrangement we would much rather replace with an upstream feature. The code is self-contained under modules/mcp_tools_translate/.

CommentFileSizeAuthor
#3 mcp_tools-add-translate-submodule.patch64.36 KBjulien

Comments

julien created an issue. See original summary.

julien’s picture

Issue summary: View changes
julien’s picture

StatusFileSize
new64.36 KB
mowens’s picture

next in the roadmap. Looking at this today.

mowens’s picture

Status: Active » Fixed

shipped in beta16. Thanks for your work on this. It was a strong contribution. Landed with a few adjustments: paragraph reference fields are discovered dynamically (the patch hardcoded two site-specific field names), translations keep the source field's text format, paragraphs is now a soft dependency (plain node translation works without it), and I completed updateTranslation() so mcp_update_content's language path works - the patch referenced it but didn't include it. Kernel-tested with and without paragraphs.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.