Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_avatar_clone_by_video tool is available.
Learn to create an AI avatar from video with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.
POST/api/app/v1/clone/avatar/by_video
Create a reusable avatar asset from an uploaded video file.
Open the Create Avatar by Video API reference →The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.
Codex-specific workflow
Use the active workspace as the source of truth. Ask Codex to identify the source video file ID and a recognizable asset title, select medux_avatar_clone_by_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.
In this workspace, use medux_avatar_clone_by_video through Medux MCP to create an AI avatar from video.
First inspect and identify the source video file ID and a recognizable asset title.
Show me the exact tool arguments before execution.
After the task completes, return the reusable avatar asset ID and verify that the avatar task completes and the returned asset belongs to the intended source video.
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.
Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the reusable avatar asset ID. The final check is explicit: confirm that the avatar task completes and the returned asset belongs to the intended source video.
Create a reusable avatar asset from an uploaded video file.
Codex selects medux_avatar_clone_by_video, presents the arguments for review, calls Medux, and reports the response.
Start with a clear instruction that names the Medux operation and the intended inputs.
Clone a reusable avatar from the uploaded source video {file id}. Title it Official avatar clone sample.Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.
| Field | Type | Requirement | Purpose |
|---|---|---|---|
file_id | string | Required | Provide the value described in the API reference. |
title | string | Optional | Provide the value described in the API reference. |
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_avatar_clone_by_video tool is available.
Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.
Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.
Check that the tool is medux_avatar_clone_by_video and that each file ID, task ID, option, and output setting matches your request before approving it.
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.
User goal
↓
Codex selects medux_avatar_clone_by_video
↓
Review inputs and approve the tool call
↓
Medux runs Create Avatar by Video
↓
Codex reports the response and outputCodex can call the medux_avatar_clone_by_video Medux MCP tool to create a reusable avatar asset from an uploaded video file. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_avatar_clone_by_video. Review its arguments before approval and consult the API reference for the current contract.
Claude-specific workflow
Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source video file ID and a recognizable asset title before proposing medux_avatar_clone_by_video. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.
Using the assets and requirements in this conversation, help me create an AI avatar from video with Medux MCP.
Restate which input fulfills each role: the source video file ID and a recognizable asset title.
Propose the medux_avatar_clone_by_video call and summarize its arguments before asking for approval.
When it finishes, return the reusable avatar asset ID with a checklist confirming that the avatar task completes and the returned asset belongs to the intended source video.
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.
Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the reusable avatar asset ID plus a concise validation checklist confirming that the avatar task completes and the returned asset belongs to the intended source video.
Create a reusable avatar asset from an uploaded video file.
Claude selects medux_avatar_clone_by_video, presents the arguments for review, calls Medux, and reports the response.
Start with a clear instruction that names the Medux operation and the intended inputs.
Clone a reusable avatar from the uploaded source video {file id}. Title it Official avatar clone sample.Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.
| Field | Type | Requirement | Purpose |
|---|---|---|---|
file_id | string | Required | Provide the value described in the API reference. |
title | string | Optional | Provide the value described in the API reference. |
Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_avatar_clone_by_video tool is available.
Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.
Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.
Check that the tool is medux_avatar_clone_by_video and that each file ID, task ID, option, and output setting matches your request before approving it.
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.
User goal
↓
Claude selects medux_avatar_clone_by_video
↓
Review inputs and approve the tool call
↓
Medux runs Create Avatar by Video
↓
Claude reports the response and outputClaude can call the medux_avatar_clone_by_video Medux MCP tool to create a reusable avatar asset from an uploaded video file. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_avatar_clone_by_video. Review its arguments before approval and consult the API reference for the current contract.