Legacy Audio to MIDI MCP Integration

For existing SSE/API key clients. This integration is not included in the public Melogen Music Intelligence ChatGPT plugin.

Legacy SSE/API key integration

Manage legacy API key

Legacy tool: convert_audio_to_midi

Existing SSE/API key clients can use this legacy tool to convert an audio file URL to MIDI. It is separate from the public Melogen Music Intelligence ChatGPT plugin.

Audio supplied by URL: MP3, WAV, FLAC, OGG, M4A

MP3WAVFLACOGGM4A

Output: MIDI

MIDI

Legacy tool parameters

file_url (required) — a URL the legacy service can access

save_stems — request separated instrument stems when supported

quantize — align MIDI notes to nearby beats when needed

How the legacy SSE/API key flow works

Use this path only if you already have a legacy SSE/API key integration; the public ChatGPT plugin uses a different product flow.

Configure your legacy MCP client

Keep your existing SSE endpoint and API key configuration. Do not use this configuration for the public ChatGPT plugin.

Call the legacy conversion tool

Ask your compatible AI client to call convert_audio_to_midi with an audio URL accessible to the legacy service.

Retrieve the MIDI result

Use the result returned through your existing client workflow, then review and edit the MIDI as needed.

Legacy client example

This prompt is for an already configured legacy SSE/API key client, not the public ChatGPT plugin.

Example prompt:

“Use convert_audio_to_midi to convert this accessible audio URL to MIDI. Keep save_stems and quantize disabled unless I request them.”

// MCP Tool Call (handled automatically by your AI agent)
{
  "tool": "convert_audio_to_midi",
  "arguments": {
    "file_url": "https://example.com/song.mp3",
    "save_stems": false,
    "quantize": false
  }
}

// Response
{
  "task_id": "xyz789",
  "status": "completed",
  "download_urls": {
    "midi": "https://api.melogenai.com/files/xyz789.mid"
  },
  "message": "Audio converted to MIDI successfully."
}

Legacy Audio to MIDI for existing clients

A maintained compatibility path for customers already using Melogen through SSE and an API key. It is not part of the public Melogen Music Intelligence ChatGPT plugin.

SSE

Legacy transport

API key

Legacy authentication

Audio → MIDI

Legacy workflow

Audio URL input

Use audio URLs in the legacy client flow for supported MP3, WAV, FLAC, OGG, and M4A files.

Polyphonic-audio workflow

Submit full mixes or songs through the existing legacy integration and review the generated MIDI.

Compatible MCP tooling

Continue using the tool with AI clients that already support your configured legacy SSE/API key connection.

MIDI output in your existing flow

Keep using the established client workflow to receive, inspect, and edit the MIDI result.

Legacy Audio to MIDI FAQ

These answers apply only to the existing SSE/API key integration, not the public Melogen Music Intelligence ChatGPT plugin.

It accepts song and mix audio, including polyphonic material. Review the resulting MIDI, especially for dense arrangements.

Limits depend on the legacy service configuration and the client that calls it. Supply a URL that the legacy service can reach.

Audio containing vocals can be submitted, but the MIDI result should be reviewed before use, particularly when vocals and instruments overlap.

When supported by the legacy service, save_stems requests separated instrument stems alongside the conversion workflow.