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.
Claude MCP tutorial · infra
How to get a Medux task by ID with Claude MCP and Medux
Use Claude and Medux through MCP to return a single Medux task record by its ID. This guide keeps file roles and constraints in context, reviews the proposed call, and validates the returned result.
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.
| Field | Type | Requirement | Purpose |
|---|---|---|---|
task_id | string | Required | Provide the value described in the API reference. |
Step-by-step workflow
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 outputFrequently 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.