Unified Codex + Claude tutorial · infra

How to get a Medux task by ID with Medux MCP

Learn to get a Medux task by ID with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

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

Return one task record by its ID.

Open the Get 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 Get a Medux Task by ID as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the exact task ID, select medux_get_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_task through Medux MCP to get a Medux task by ID.
First inspect and identify the exact task ID.
Show me the exact tool arguments before execution.
After the task completes, return the matching task record and verify that the response ID matches the request and the 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 matching task record. The final check is explicit: confirm that the response ID matches the request and the status is interpreted correctly.

What this tutorial does

Medux operation

Return one task record by its ID.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires a task id from account history or task creation responses.
  • Useful for account-side history views.

Prompt Codex

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

Use Medux to run Get Task. Review the required inputs, call medux_get_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_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 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_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_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Get Task
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Get Task API through MCP?

Codex can call the medux_get_task Medux MCP tool to return one task record by its ID. 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_task. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Get a Medux Task by ID as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the exact task ID before proposing medux_get_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 get a Medux task by ID with Medux MCP.
Restate which input fulfills each role: the exact task ID.
Propose the medux_get_task call and summarize its arguments before asking for approval.
When it finishes, return the matching task record with a checklist confirming that the response ID matches the request and the 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 matching task record plus a concise validation checklist confirming that the response ID matches the request and the status is interpreted correctly.

What this tutorial does

Medux operation

Return one task record by its ID.

Agent workflow

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

Before you start

Authentication

  • Authentication is required via Authorization header.

Preconditions

  • Requires a task id from account history or task creation responses.
  • Useful for account-side history views.

Prompt Claude

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

Use Medux to run Get Task. Review the required inputs, call medux_get_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_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 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_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_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Get Task
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Get Task API through MCP?

Claude can call the medux_get_task Medux MCP tool to return one task record by its ID. 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_task. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I get a Medux task by ID with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_get_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 get a Medux task by ID

This tutorial addresses developer workflows for AI media task status API and get asynchronous task by ID 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 infrastructure step supports long-running image-to-video, AI lip sync, and video watermark-removal jobs by keeping uploads, task IDs, status checks, and returned media auditable.

Run an asynchronous image-to-video jobRun an AI lip sync taskRun video watermark removal
Can Codex or Claude get a Medux task by ID 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

Build a privacy-conscious, auditable workflow to get a Medux task by ID

This infrastructure step belongs to a unified, multi-model AI media API workflow for Codex MCP, Claude MCP, and other agents. Use one authorized API context, keep task and asset IDs in the calling system, poll asynchronous work, and return only the media result required by the application.

Privacy-conscious operation means keeping credentials outside prompts, uploading only necessary files, limiting access, and defining retention and deletion rules in your own application. Do not infer undocumented encryption, retention, webhook, or compliance guarantees from this tutorial.

How does task polling support production AI media workflows?

Store the Medux task ID, poll until a terminal state, handle failure without duplicate submissions, and attach the accepted result to the originating application record.

Build with the API

API reference and official examples