Unified Codex + Claude tutorial · generate

How to create a talking photo from image and audio with Medux MCP

Learn to create a talking photo from image and audio with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/generate/video/image_audio_driven

Generate a talking video from a reference image, driving audio, and prompt text.

Open the Create Image Audio Driven Video API reference →
Choose your AI client

Follow the Codex or Claude workflow

The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.

Codex-specific workflow

Run Talking Photo AI as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the portrait image, driving audio, and prompt text, select medux_image_audio_driven_video, and keep the Medux task ID and returned output with the rest of the project. Naming the input roles and the expected result prevents an agent from guessing which file should be used where.

Codex prompt pattern

In this workspace, use medux_image_audio_driven_video through Medux MCP to create a talking photo from an image and audio.
First inspect and identify the portrait image, driving audio, and prompt text.
Show me the exact tool arguments before execution.
After the task completes, return the generated talking-photo video and verify that the portrait follows the driving audio and the returned video plays correctly.

Approval gate

Before approving the call, compare the selected tool, file or asset IDs, ordering, timing, and output settings with the request. If a local filename was mapped to an uploaded Medux file ID, keep that mapping visible so it can be audited later.

Result verification

Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the generated talking-photo video. The final check is explicit: confirm that the portrait follows the driving audio and the returned video plays correctly.

What this tutorial does

Medux operation

Generate a talking video from a reference image, driving audio, and prompt text.

Agent workflow

Codex selects medux_image_audio_driven_video, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Upload the source file and create a file reference before calling this endpoint.
  • Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
  • All file inputs must be uploaded and persisted as file references before submission.

Prompt Codex

Start with a clear instruction that names the Medux operation and the intended inputs.

Generate a talking video from a reference image, driving audio, and prompt text.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
prompt_textstringRequiredTalking prompt text used to guide video generation.
prompt_image_file_idstringRequiredReference image file id.
prompt_audio_file_idstringRequiredDriving audio file id.
resolutionstringOptionalPrompt image or prompt video frame resize target before generation. Default: 720p.
model_idstringOptionalImage audio driven video model id. Default: image-audio-driven-video-default.
titlestringOptionalOptional task title.

Step-by-step workflow

01

Connect Medux MCP to Codex

Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_image_audio_driven_video tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Codex to run Create Image Audio Driven Video

Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_image_audio_driven_video and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Codex selects medux_image_audio_driven_video
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Image Audio Driven Video
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Create Image Audio Driven Video API through MCP?

Codex can call the medux_image_audio_driven_video Medux MCP tool to generate a talking video from a reference image, driving audio, and prompt text. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_image_audio_driven_video. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Talking Photo AI as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the portrait image, driving audio, and prompt text before proposing medux_image_audio_driven_video. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.

Claude prompt pattern

Using the assets and requirements in this conversation, help me create a talking photo from an image and audio with Medux MCP.
Restate which input fulfills each role: the portrait image, driving audio, and prompt text.
Propose the medux_image_audio_driven_video call and summarize its arguments before asking for approval.
When it finishes, return the generated talking-photo video with a checklist confirming that the portrait follows the driving audio and the returned video plays correctly.

Context checkpoint

Have Claude summarize the intended transformation, identify every source asset by role, and list the important constraints. Review that summary together with the proposed tool arguments; correct the conversation first if a file, order, time range, or setting is ambiguous.

Result verification

Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the generated talking-photo video plus a concise validation checklist confirming that the portrait follows the driving audio and the returned video plays correctly.

What this tutorial does

Medux operation

Generate a talking video from a reference image, driving audio, and prompt text.

Agent workflow

Claude selects medux_image_audio_driven_video, presents the arguments for review, calls Medux, and reports the response.

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Upload the source file and create a file reference before calling this endpoint.
  • Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
  • All file inputs must be uploaded and persisted as file references before submission.

Prompt Claude

Start with a clear instruction that names the Medux operation and the intended inputs.

Generate a talking video from a reference image, driving audio, and prompt text.

Request fields to review

Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.

FieldTypeRequirementPurpose
prompt_textstringRequiredTalking prompt text used to guide video generation.
prompt_image_file_idstringRequiredReference image file id.
prompt_audio_file_idstringRequiredDriving audio file id.
resolutionstringOptionalPrompt image or prompt video frame resize target before generation. Default: 720p.
model_idstringOptionalImage audio driven video model id. Default: image-audio-driven-video-default.
titlestringOptionalOptional task title.

Step-by-step workflow

01

Connect Medux MCP to Claude

Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_image_audio_driven_video tool is available.

02

Prepare the required inputs

Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.

03

Ask Claude to run Create Image Audio Driven Video

Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.

04

Review and approve the tool call

Check that the tool is medux_image_audio_driven_video and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.

Workflow recap

User goal
  ↓
Claude selects medux_image_audio_driven_video
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Image Audio Driven Video
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Create Image Audio Driven Video API through MCP?

Claude can call the medux_image_audio_driven_video Medux MCP tool to generate a talking video from a reference image, driving audio, and prompt text. This guide covers the required inputs, approval flow, result handling, and the matching API reference.

Which MCP tool does this tutorial use?

This workflow uses medux_image_audio_driven_video. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I create a talking photo from image and audio with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_image_audio_driven_video call, and verify the returned result. The tabs above keep client-specific prompting on one canonical page.

To compare talking-photo inputs with a reusable lip-sync pipeline, read how to create AI lip sync video online.

Can I use the same Medux tool in Codex and Claude?

Yes. The client interaction differs, but both use the same Medux MCP tool and API request contract shown in this tutorial.

Related developer intent

Use AI agents to create a talking photo from image and audio

This tutorial addresses developer workflows for talking photo API and animate a photo with audio by making the task repeatable through the Medux API. Codex or Claude can prepare inputs, show the MCP tool arguments for approval, monitor processing, and return an output that can be checked against the original request.

This capability also fits a broader AI lip sync and talking-avatar pipeline: prepare an approved voice or avatar asset, run audio-to-video lip sync, then verify timing, mouth motion, and final playback.

Can Codex or Claude create a talking photo from image and audio through Medux MCP?

Yes. Use the client-specific tab above to prepare the inputs, review the Medux tool call, run the operation, and verify the returned result. The linked API reference remains the source of truth for supported fields and limits.

Production, trust, and developer intent

Add consent and review controls when you create a talking photo from image and audio

Treat this as a consent-based, auditable workflow for create a talking photo from image and audio. Use only a voice, face, avatar, or reference asset that you own or have explicit permission to process; keep the source authorization, approved prompt, Medux task ID, and accepted output together for later review.

For production use, pair the Medux API with your own consent records, identity checks, access controls, retention rules, and human approval. These tutorials promote responsible AI media use but do not claim automatic consent verification.

What makes an AI avatar or voice workflow consent-based?

Document who authorized the source material, restrict who can submit tasks, keep the approved inputs and output together, and require review before publishing or reusing a likeness or voice.