Unified Codex + Claude tutorial · clone

How to clone a reusable AI voice with Medux MCP

Learn to clone a reusable AI voice with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/clone/voice

Create a reusable voice asset from an uploaded audio file.

Open the Create Voice 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 Create a Reusable AI Voice as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the clean voice sample, language details, and a recognizable voice title, select medux_clone_voice, 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_clone_voice through Medux MCP to create a reusable AI voice.
First inspect and identify the clean voice sample, language details, and a recognizable voice title.
Show me the exact tool arguments before execution.
After the task completes, return the reusable voice asset ID and verify that the cloning task completes and the returned voice asset matches the intended sample.

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 reusable voice asset ID. The final check is explicit: confirm that the cloning task completes and the returned voice asset matches the intended sample.

What this tutorial does

Medux operation

Create a reusable voice asset from an uploaded audio file.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires an uploaded source file id.
  • Use a clean speech sample for better identity consistency.

Prompt Codex

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

Clone a reusable voice from the uploaded audio file {file id}. Title it Official voice clone sample.

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
file_idstringRequiredProvide the value described in the API reference.
titlestringOptionalProvide the value described in the API reference.

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_clone_voice 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 Voice

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_clone_voice 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_clone_voice
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Voice
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Create Voice API through MCP?

Codex can call the medux_clone_voice Medux MCP tool to create a reusable voice asset from an uploaded audio file. 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_clone_voice. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Create a Reusable AI Voice as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the clean voice sample, language details, and a recognizable voice title before proposing medux_clone_voice. 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 reusable AI voice with Medux MCP.
Restate which input fulfills each role: the clean voice sample, language details, and a recognizable voice title.
Propose the medux_clone_voice call and summarize its arguments before asking for approval.
When it finishes, return the reusable voice asset ID with a checklist confirming that the cloning task completes and the returned voice asset matches the intended sample.

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 reusable voice asset ID plus a concise validation checklist confirming that the cloning task completes and the returned voice asset matches the intended sample.

What this tutorial does

Medux operation

Create a reusable voice asset from an uploaded audio file.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires an uploaded source file id.
  • Use a clean speech sample for better identity consistency.

Prompt Claude

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

Clone a reusable voice from the uploaded audio file {file id}. Title it Official voice clone sample.

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
file_idstringRequiredProvide the value described in the API reference.
titlestringOptionalProvide the value described in the API reference.

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_clone_voice 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 Voice

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_clone_voice 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_clone_voice
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Voice
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Create Voice API through MCP?

Claude can call the medux_clone_voice Medux MCP tool to create a reusable voice asset from an uploaded audio file. 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_clone_voice. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I clone a reusable AI voice with Medux MCP?

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

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 clone a reusable AI voice

This tutorial addresses developer workflows for voice cloning API and clone a reusable AI voice 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.

Build an AI lip sync video with Medux MCPCreate a talking photo from image and audio
Can Codex or Claude clone a reusable AI voice 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.

Responsible voice cloning

Build a responsible voice cloning API workflow

Use only your own voice or reference audio for which you have explicit permission. Keep the consent record, source audio, approved script, Medux task ID, and accepted output together so the AI voice workflow remains auditable in Codex or Claude.

A security-conscious voice workflow also keeps API keys outside prompts, limits access to voice assets, defines retention, and requires listening review before publishing or reuse.

Does this workflow provide automatic voice-consent verification?

No automatic verification is documented here. The integrating application must collect permission, protect the source audio, restrict use, and prevent misleading or unauthorized cloning.

Build with the API

API reference and official examples