Can I create a presigned upload URL with both Codex and Claude?

Yes. Codex and Claude can use medux_create_upload_url through Medux MCP. Choose the matching tab for client-specific prompting while using the same Medux operation and request contract.

Which Medux MCP tool does this tutorial use?

This workflow uses medux_create_upload_url. Review the linked API reference for the current request and response contract.

Unified Codex + Claude tutorial · get-started

How to create a presigned upload URL with Medux MCP

Learn to create a presigned upload URL with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/upload_urls

Create a pre-signed upload URL and file reference for a direct client upload.

Open the Create Upload URL 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 Create a Presigned Upload URL as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the source filename, media type, and upload purpose, select medux_create_upload_url, 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_create_upload_url through Medux MCP to create a presigned upload URL.
First inspect and identify the source filename, media type, and upload purpose.
Show me the exact tool arguments before execution.
After the task completes, return the upload URL and Medux file reference and verify that the URL accepts the intended file and the returned file reference is saved for the next call.

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 upload URL and Medux file reference. The final check is explicit: confirm that the URL accepts the intended file and the returned file reference is saved for the next call.

What this tutorial does

Medux operation

Create a pre-signed upload URL and file reference for a direct client upload.

Agent workflow

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

Before you start

Authentication

Authentication is required via Authorization header.

Preconditions

Try it is available after login because the returned upload target is account-scoped.
Use this as the first step in most Playground and agent flows.

Prompt Codex

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

Use Medux to run Create Upload URL. Review the required inputs, call medux_create_upload_url, 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
`extension`	string	Optional	File extension without a leading dot, such as mp4.
`media_type`	string	Optional	Media type used to validate the file extension and build the upload object path. Use a supported Medux media type and check the linked API reference for the current enum values.

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_create_upload_url 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 Create Upload URL

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_create_upload_url 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_create_upload_url
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Upload URL
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux Create Upload URL API through MCP?

Codex can call the medux_create_upload_url Medux MCP tool to create a pre-signed upload URL and file reference for a direct client upload. 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_create_upload_url. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Create a Presigned Upload URL as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source filename, media type, and upload purpose before proposing medux_create_upload_url. 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 create a presigned upload URL with Medux MCP.
Restate which input fulfills each role: the source filename, media type, and upload purpose.
Propose the medux_create_upload_url call and summarize its arguments before asking for approval.
When it finishes, return the upload URL and Medux file reference with a checklist confirming that the URL accepts the intended file and the returned file reference is saved for the next call.

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 upload URL and Medux file reference plus a concise validation checklist confirming that the URL accepts the intended file and the returned file reference is saved for the next call.

What this tutorial does

Medux operation

Create a pre-signed upload URL and file reference for a direct client upload.

Agent workflow

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

Before you start

Authentication

Authentication is required via Authorization header.

Preconditions

Try it is available after login because the returned upload target is account-scoped.
Use this as the first step in most Playground and agent flows.

Prompt Claude

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

Use Medux to run Create Upload URL. Review the required inputs, call medux_create_upload_url, 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
`extension`	string	Optional	File extension without a leading dot, such as mp4.
`media_type`	string	Optional	Media type used to validate the file extension and build the upload object path. Use a supported Medux media type and check the linked API reference for the current enum values.

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_create_upload_url 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 Create Upload URL

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_create_upload_url 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_create_upload_url
  ↓
Review inputs and approve the tool call
  ↓
Medux runs Create Upload URL
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux Create Upload URL API through MCP?

Claude can call the medux_create_upload_url Medux MCP tool to create a pre-signed upload URL and file reference for a direct client upload. 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_create_upload_url. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I create a presigned upload URL with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_create_upload_url 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 create a presigned upload URL

This tutorial addresses developer workflows for presigned upload URL media API and upload media for AI video 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 job Run an AI lip sync task Run video watermark removal

Can Codex or Claude create a presigned upload URL 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.

Privacy-conscious media upload

Use presigned upload URLs for AI media workflows

A presigned upload URL lets an authorized Codex or Claude workflow transfer the specific source file needed for an AI media task without placing the media bytes or API key in the prompt. Upload only the approved file, keep the asset mapping visible, and use the URL before it expires.

Privacy-conscious handling still requires access controls, minimal uploads, credential management, and retention or deletion rules in the integrating application; this page does not assert undocumented compliance guarantees.

Should an AI agent store a presigned upload URL?

Treat it as short-lived sensitive data. Use it for the intended file and operation, avoid logging it unnecessarily, and do not reuse it after expiration.

Build with the API

API reference and official examples

Create Upload URL API referenceCurrent request fields, response data, limits, and examples.
Official Codex workflow exampleClient-specific prompt, approval, and result-verification example.
Official Claude workflow exampleClient-specific prompt, approval, and result-verification example.