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

Claude can use medux_sync_task through Medux MCP to sync a task with its upstream provider and return the latest local state. The workflow keeps input roles and constraints in context, reviews the proposed call, and checks the returned result.

Claude MCP tutorial · infra

How to sync a Medux task with Claude 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 Claude and Medux through MCP to sync a task with its upstream provider and return the latest local state. This guide keeps file roles and constraints in context, reviews the proposed call, and validates the returned result.

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 →

Claude-specific workflow

Run Sync a Medux Task 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_sync_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 sync a Medux task with Medux MCP.
Restate which input fulfills each role: the exact task ID.
Propose the medux_sync_task call and summarize its arguments before asking for approval.
When it finishes, return the refreshed Medux task record with a checklist confirming that the response belongs to the requested task and reflects the latest provider state.

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 refreshed Medux task record plus a concise validation checklist confirming 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

Claude 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 Claude

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 Claude

Add the Medux remote MCP endpoint to Claude, 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 Claude to run Sync Task

Use one direct instruction with the intended values. Claude 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
  ↓
Claude selects medux_sync_task
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Sync Task
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Sync Task API through MCP?

Claude 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.