01
Open the project in Codex
Start inside the folder that contains your avatar video and audio file. In the operation video, Codex first checks the workspace so it knows exactly which files can be used for the Medux task.
Before you start
Keep the setup small. The operation video uses a short avatar clip and a WAV audio file, then asks Codex to operate Medux through the MCP connection.
1. A source avatar videoUse a clear front-facing or slightly angled video. The face should be visible, stable, and not heavily blocked by hands, captions, or UI overlays.
2. A speech audio fileUse a clean WAV or MP3 file. The audio drives the mouth timing, so avoid long silence, heavy background music, or overlapping voices.
3. Codex with MCP accessConnect Codex to the Medux MCP server using the configuration from your Medux account or internal setup guide.
4. A clear output nameSave the result with a simple name such as
lip_synced_avatar.mp4 so it is easy to preview and reuse.# Example project layout
project/
avatar.mp4
reference_voice.wav
tts.txt
config/
output/The Medux MCP flow
The operation is straightforward: Codex reads your goal, checks the files, chooses the Medux tools, uploads media, creates the generation task, polls the task status, and saves the final video locally.
Codex reads the request
MCP connects to Medux
Files are uploaded
Medux renders
MP4 is returned
Step-by-step tutorial
02
Connect Medux as an MCP tool
Make sure the Medux MCP server is enabled before asking Codex to run the workflow. Once MCP is connected, Codex can call Medux directly instead of making you switch dashboards or write a separate upload script.
Tip: Keep your API key outside the prompt. Store it in your local MCP configuration or environment variables.
# Example only: use the exact MCP config from your Medux account
export MEDUX_API_KEY="your_medux_api_key"
# Then start Codex in the folder that contains your media files
codex03
Ask Codex to run the lip-sync job
Use one direct instruction. The best prompt names the input files, explains the goal, and tells Codex what to return. This keeps the tool call clean and reduces back-and-forth.
Use Medux through MCP to create a lip-synced avatar video.
Inputs:
- avatar.mp4
- reference_voice.wav
Please upload both files to Medux, create the required avatar source, generate a lip-and-tongue synced video from the audio, poll the task until it is complete, and download the final MP4 as output/lip_synced_avatar.mp4.
04
Let Codex upload the media and create the source avatar
Codex uses the Medux MCP tools to create upload slots, send the video and audio, and prepare the avatar source. In practice, this is the part that replaces manual dashboard uploads.
05
Run the audio-driven talking-head task
After the avatar source is ready, Codex launches the generation task. Medux uses the video as the visual identity and the audio as the timing reference, then renders a synced output.
06
Poll the task until Medux returns the result
Do not refresh manually. Codex can keep checking the Medux task status and continue only when the render is finished. This is especially useful for longer videos or higher-quality outputs.
07
Download and preview the final MP4
When the task is complete, Codex downloads the output and saves it locally. Open the result and check three things: the mouth follows the audio, the face remains stable, and the final video plays from start to finish.
# Quick local check
ffprobe output/lip_synced_avatar.mp4
# Preview the generated video
open output/lip_synced_avatar.mp4
Quality checklist
Use this checklist before publishing the result or adding it to a larger content workflow.
Face visibilityThe face should remain visible throughout the clip. Avoid shots where the mouth is covered or too small.
Audio claritySpeech should be clean and centered. Remove long silence before sending the audio to Medux.
Timing reviewWatch the first few seconds and a later section. Make sure the mouth still follows the voice after the midpoint.
Final exportUse a practical MP4 filename, then keep both the source files and the output in the same project folder for repeatability.
Publish-ready summary
Medux gives Codex a media workflow layer through MCP. For lip and tongue sync, Codex only needs the source video, the speech audio, and a clear instruction. Medux handles the rendering, while Codex handles the tool calls, task tracking, and final download.
No separate dashboard hopping
No manual API upload script
One prompt to final synced video
Example result
Final lip-sync result
Below is the final lip-synced avatar video generated by Medux after Codex completes the MCP workflow.
Explore related workflows
Continue with a nearby Medux workflow or compare how the same task works across Claude MCP and Codex MCP.