How do I run Sync a Medux Task with Codex MCP?

Codex can use medux_sync_task through Medux MCP to sync a task with its upstream provider and return the latest local state. The workflow identifies the exact inputs, reviews the tool arguments, monitors processing, and verifies the returned result.

Codex MCP tutorial · infra

How to sync a Medux task with Codex MCP and Medux

Q: Which MCP tool does this tutorial use?

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

Use Codex and Medux through MCP to sync a task with its upstream provider and return the latest local state. This guide covers input preparation, the approval gate, task monitoring, and a concrete output check.

POST/api/app/v1/tasks/{task_id}/sync

Sync the task with the upstream provider and return the latest local state.

Open the Sync Task API reference →

Codex-specific workflow

Run Sync a Medux Task as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the exact task ID, select medux_sync_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_sync_task through Medux MCP to sync a Medux task.
First inspect and identify the exact task ID.
Show me the exact tool arguments before execution.
After the task completes, return the refreshed Medux task record and verify that the response belongs to the requested task and reflects the latest provider state.

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 refreshed Medux task record. The final check is explicit: confirm that the response belongs to the requested task and reflects the latest provider state.

What this tutorial does

Medux operation

Sync the task with the upstream provider and return the latest local state.

Agent workflow

Codex selects medux_sync_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 created by a clone, generate, or process request.
Use this when you want to refresh task state outside the default polling loop.

Prompt Codex

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

Use Medux to run Sync Task. Review the required inputs, call medux_sync_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.

Field	Type	Requirement	Purpose
`task_id`	string	Required	Provide the value described in the API reference.

Step-by-step workflow

Connect Medux MCP to Codex

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

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.

Ask Codex to run Sync Task

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

Review and approve the tool call

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

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_sync_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Sync Task
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Sync Task API through MCP?

Codex can call the medux_sync_task Medux MCP tool to sync the task with the upstream provider and return the latest local state. 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_sync_task. Review its arguments before approval and consult the API reference for the current contract.