Unified Codex + Claude tutorial · clone

How to check a voice cloning task with Medux MCP

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

GET/api/app/v1/clone/voice/tasks/{task_id}

Return the current state of a voice cloning task.

Open the Get Voice Task 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 Check a Voice Cloning Task as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the voice cloning task ID, select medux_get_voice_task, 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_get_voice_task through Medux MCP to check a voice cloning task.
First inspect and identify the voice cloning task ID.
Show me the exact tool arguments before execution.
After the task completes, return the latest voice task state and result identifiers and verify that the response belongs to the requested task and its status is interpreted 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 latest voice task state and result identifiers. The final check is explicit: confirm that the response belongs to the requested task and its status is interpreted correctly.

What this tutorial does

Medux operation

Return the current state of a voice cloning task.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Try it requires a task id returned by a voice operation.
  • Poll the task after voice clone or parameter edit requests.

Prompt Codex

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

Use Medux to run Get Voice Task. Review the required inputs, call medux_get_voice_task, wait for the result if a task is returned, and report the output clearly.

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
task_idstringRequiredProvide 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_get_voice_task tool is available.

02

Prepare the required inputs

Identify the account, task, asset, or filter values the operation needs. Confirm that the Medux API key is available to the MCP connection.

03

Ask Codex to run Get Voice Task

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_get_voice_task and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

Ask the agent to report the task status, result references, errors, and next action in a concise summary.

Workflow recap

User goal
  ↓
Codex selects medux_get_voice_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Get Voice Task
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Get Voice Task API through MCP?

Codex can call the medux_get_voice_task Medux MCP tool to return the current state of a voice cloning task. 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_get_voice_task. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Check a Voice Cloning Task as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the voice cloning task ID before proposing medux_get_voice_task. 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 check a voice cloning task with Medux MCP.
Restate which input fulfills each role: the voice cloning task ID.
Propose the medux_get_voice_task call and summarize its arguments before asking for approval.
When it finishes, return the latest voice task state and result identifiers with a checklist confirming that the response belongs to the requested task and its status is interpreted 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 latest voice task state and result identifiers plus a concise validation checklist confirming that the response belongs to the requested task and its status is interpreted correctly.

What this tutorial does

Medux operation

Return the current state of a voice cloning task.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Try it requires a task id returned by a voice operation.
  • Poll the task after voice clone or parameter edit requests.

Prompt Claude

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

Use Medux to run Get Voice Task. Review the required inputs, call medux_get_voice_task, wait for the result if a task is returned, and report the output clearly.

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
task_idstringRequiredProvide 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_get_voice_task tool is available.

02

Prepare the required inputs

Identify the account, task, asset, or filter values the operation needs. Confirm that the Medux API key is available to the MCP connection.

03

Ask Claude to run Get Voice Task

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_get_voice_task and that each file ID, task ID, option, and output setting matches your request before approving it.

05

Check the Medux response

Ask the agent to report the task status, result references, errors, and next action in a concise summary.

Workflow recap

User goal
  ↓
Claude selects medux_get_voice_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Get Voice Task
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Get Voice Task API through MCP?

Claude can call the medux_get_voice_task Medux MCP tool to return the current state of a voice cloning task. 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_get_voice_task. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I check a voice cloning task with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_get_voice_task 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 check a voice cloning task

This tutorial addresses developer workflows for voice cloning task status API and check AI voice clone progress 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 audioPrepare a reusable voice for avatar workflows
Can Codex or Claude check a voice cloning task 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 check a voice cloning task

Treat this as a consent-based, auditable workflow for check a voice cloning task. 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.

Build with the API

API reference and official examples