The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.
Codex-specific workflow
Run Shift Audio Pitch as a Codex MCP task
Use the active workspace as the source of truth. Ask Codex to identify the source audio and exact pitch-shift value, select medux_shift_audio_pitch, 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_shift_audio_pitch through Medux MCP to shift audio pitch.
First inspect and identify the source audio and exact pitch-shift value.
Show me the exact tool arguments before execution.
After the task completes, return the pitch-shifted audio and verify that the pitch changed by the requested amount and the audio remains complete.
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 pitch-shifted audio. The final check is explicit: confirm that the pitch changed by the requested amount and the audio remains complete.
What this tutorial does
Medux operation
Shift the pitch of an audio file.
Agent workflow
Codex selects medux_shift_audio_pitch, presents the arguments for review, calls Medux, and reports the response.
Before you start
Authentication
Authentication is required via Authorization header.
Preconditions
Upload the source file and create a file reference before calling this endpoint.
Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
All file inputs must be uploaded and persisted as file references before submission.
Prompt Codex
Start with a clear instruction that names the Medux operation and the intended inputs.
Shift the pitch of an audio file.
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.
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_shift_audio_pitch tool is available.
02
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.
03
Ask Codex to run Shift Audio Pitch
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_shift_audio_pitch and that each file ID, task ID, option, and output setting matches your request before approving it.
05
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_shift_audio_pitch
↓
Review inputs and approve the tool call
↓
Medux runs Shift Audio Pitch
↓
Codex reports the response and output
Frequently asked questions
Can Codex use the Medux Shift Audio Pitch API through MCP?
Codex can call the medux_shift_audio_pitch Medux MCP tool to shift the pitch of an audio file. 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_shift_audio_pitch. Review its arguments before approval and consult the API reference for the current contract.
Claude-specific workflow
Run Adjust Audio Pitch as a Claude MCP workflow
Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source audio and the requested semitone or pitch change before proposing the Medux audio pitch tool. 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 adjust audio pitch with Medux MCP.
Restate which input fulfills each role: the source audio and the requested semitone or pitch change.
Propose the the Medux audio pitch tool call and summarize its arguments before asking for approval.
When it finishes, return the pitch-adjusted audio file with a checklist confirming that the pitch changed by the requested amount and the audio remains complete.
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 pitch-adjusted audio file plus a concise validation checklist confirming that the pitch changed by the requested amount and the audio remains complete.
Before you start
Connect Medux to Claude
Make sure the Medux MCP connector is enabled and available in the current Claude workspace.
Prepare the source audio
Place your file in a local project folder. The video uses sample-audio.m4a.
project/
└── sample-audio.m4a
The workflow
Describe the task
Create upload URL
Upload audio
Run two pitch shifts
Download results
01
Describe both pitch changes in one prompt
Ask Claude to use Medux and specify the exact change for each output. In the tutorial, the source file is shifted up by 100% and down by 50%.
Use Medux to modify the pitch of sample-audio.m4a.
Create two outputs:
- Increase pitch by 100% (2× frequency / +12 semitones)
- Decrease pitch by 50% (0.5× frequency / −12 semitones)
Upload the file with curl when needed.
Why semitones? A one-octave shift equals 12 semitones. Using +12 or −12 makes the requested change unambiguous.
02
Let Claude request an upload URL from Medux
Claude calls the Medux file tool through MCP and receives a temporary upload URL. If the remote storage endpoint cannot be reached from Claude’s sandbox, Claude can provide a local curl command instead.
The workflow falls back to a local upload command when the sandbox cannot reach the storage endpoint.
03
Upload the audio with a width-safe command
Run the generated command from the folder containing the audio file. The command below is intentionally split across lines so it remains readable on desktop and mobile layouts.
Recommended check: play both files and confirm that duration, loudness, and intelligibility remain suitable for your use case.
What this workflow removes
You do not need to open a separate media dashboard, write a custom API client, or manually manage two independent processing jobs. Claude coordinates the steps; Medux handles the audio transformation.
✓ One natural-language request
✓ Two outputs in parallel
✓ Local downloadable MP3 files
Reusable prompt
Replace the filename and semitone values to reuse the same workflow for other audio files.
Use Medux through MCP to adjust the pitch of [AUDIO_FILE].
Create these versions:
- [SEMITONES_UP] semitones higher
- [SEMITONES_DOWN] semitones lower
Upload the source with curl if the sandbox cannot access the upload endpoint.
Poll both tasks until completion, then provide commands to download the results.
Explore related workflows
Continue with a nearby Medux workflow or compare how the same task works across Claude MCP and Codex MCP.
Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_shift_audio_pitch 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 shift audio pitch
This tutorial addresses developer workflows for audio pitch changer API and shift voice pitch 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 capability also fits a broader AI lip sync and talking-avatar pipeline: prepare an approved voice or avatar asset, run audio-to-video lip sync, then verify timing, mouth motion, and final playback.
Can Codex or Claude shift audio pitch 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
Use an auditable audio workflow to shift audio pitch
This AI audio processing API workflow lets Codex or Claude shift audio pitch while keeping file roles, tool arguments, task IDs, and output checks visible. Use authorized source audio and preserve an input-to-output record when the result feeds voice, dubbing, lip sync, or production video.
A security-conscious audio workflow keeps API keys outside prompts, limits uploaded media to what the task needs, and restricts result access in the calling application. Those operational controls complement the Medux tool call.
How do I make an AI audio workflow easier to audit?
Keep the source asset ID, approved parameters, Medux task ID, returned result, and final listening check together with the project that requested the edit.
