How the workflow works
Claude handles orchestration. Medux handles image processing. MCP connects the two, keeping the task inside one agent workflow instead of requiring a separate dashboard or custom integration.
Prerequisites
swap_head_src.jpg contains the head or identity to transfer.
swap_head_target.jpg provides the body, pose, clothing, and scene to preserve.
Place both images in a project folder Claude can access.
Enable the Medux connector before starting the task.
Step-by-step guide
Give Claude one precise instruction
Tell Claude which image supplies the new head, which image receives it, and that Medux must be called through MCP. The recording also asks Claude to upload the files with curl.
Swap the head in "swap_head_src.jpg" with the head in
"swap_head_target.jpg". Use Medux through MCP, upload the
files with curl, run the head-swap task, and save the result
in the current project folder.Source, reference, and generated result
Compare the three images below to see how the source image, target reference, and final Medux output relate to one another.



Reusable prompt
Replace the filenames and output path to reuse this workflow.
I have two images in this project:
- [SOURCE_IMAGE] contains the head to transfer.
- [TARGET_IMAGE] contains the body and scene to preserve.
Use the Medux MCP tools to create separate image upload URLs.
Upload both files with curl. Then run the Medux Head Swap task,
wait for completion, and save the final image as [OUTPUT_FILE].
Preserve the target pose, clothing, lighting, and background.Pre-publish checklist
Before using the result on a public page, campaign, or product workflow, review the image carefully and confirm that you have permission to use both source images.
Explore related workflows
Continue with a nearby Medux workflow or compare how the same task works across Claude MCP and Codex MCP.
