Mix a song from Claude, Cursor, or Codex with MCP

MCP, the Model Context Protocol, lets an AI assistant use a tool the way you would use a button. Orbit Waves speaks MCP, so Claude, Cursor, Codex, or any other MCP client can open your song, split it, set the loudness, add an EQ, and save a master.

Connect in a minute

• Open Settings in Orbit Waves and create a key. It is shown once.
• Add the endpoint: this site plus /api/mcp, with the header Authorization: Bearer and your key.
• Connect has ready-made configs for Claude, Cursor, and Codex, and a local orbit-waves-mcp command for other clients.
• One key works in every client.

What to ask

A good first sentence: “Open my latest Orbit Waves project, split it, and make it radio-ready for Spotify.” The assistant lists your projects newest first, splits the song, runs the same finish the button runs, and reports the loudness.

Then be specific: “Turn the vocal up 2 dB and add a little room to it.” “Write a volume ramp on the drums over the first eight seconds.” “Compare the original loudness with the mix.” A tool can add effects the page does not put on a button: EQ, compressor, limiter, gate, de-esser, reverb, delay, chorus, saturation, width, and filter, plus buses, sends, and automation.

You stay in charge

The page and the assistant call the same actions on one project document. A change made in chat appears on the open mix within a couple of seconds and lands in History marked Tool. Every batch is one undo, so Command-Z takes back whatever the assistant just did. The tool cannot invent a feature the app does not have.