PostFader V12 — FL Studio MCP Server

by synopsys0

Overview Schema Source Related Servers Discussions Admin

Python

Local

audio_transcribe_melody

Read-onlyIdempotent

Convert a monophonic audio file into notes in beats. Review the sequence, then write it to a piano roll or export MIDI.

Instructions

Transcribe a monophonic recording (a sung or played line) into notes.

Reads the file only. Returns a note sequence in beats, ready to review and
then write with piano_roll_write_notes or export with compose_export_midi.
Chords and full mixes transcribe poorly; give it one isolated line.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Absolute path to one isolated, monophonic pitched source.
`fmax_hz`	No	Highest pitch to track, in Hz.
`fmin_hz`	No	Lowest pitch to track, in Hz.
`tempo_bpm`	No	Tempo for beat positions; estimated when omitted, 120 if estimation fails.
`max_seconds`	No	Seconds of audio to transcribe.
`quantize_grid_beats`	No	Snap grid in beats; null keeps raw timing.
`minimum_note_seconds`	No	Shorter detected notes are dropped.

Output Schema

TableJSON Schema

Name	Required	Default
`method`	No	frame-autocorrelation-segmentation-1
`fmax_hz`	Yes
`fmin_hz`	Yes
`sequence`	Yes
`limitations`	Yes
`source_path`	Yes
`tempo_source`	Yes
`source_sha256`	Yes
`schema_version`	No	1.0
`tempo_bpm_used`	Yes
`transcribed_at`	Yes
`frame_hop_seconds`	Yes
`mutations_applied`	No
`voiced_frame_share`	Yes
`median_pitch_confidence`	Yes
`analyzed_duration_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed52 schema fields changedv11.0.2Oct 5, 2026
- addedInput schema / properties / fmax_hz / description
```
Added value: +"Highest pitch to track, in Hz."
```
- addedInput schema / properties / fmin_hz / description
```
Added value: +"Lowest pitch to track, in Hz."
```
- addedInput schema / properties / max_seconds / description
```
Added value: +"Seconds of audio to transcribe."
```
- addedInput schema / properties / minimum_note_seconds / description
```
Added value: +"Shorter detected notes are dropped."
```
- changedInput schema / properties / path / description
```
Previous value: -"Absolute path to one isolated pitched source."New value: +"Absolute path to one isolated, monophonic pitched source."
```
- addedInput schema / properties / quantize_grid_beats / description
```
Added value: +"Snap grid in beats; null keeps raw timing."
```
- addedInput schema / properties / tempo_bpm / description
```
Added value: +"Tempo for beat positions; estimated when omitted, 120 if estimation fails."
```
- removedOutput schema / $defs / CreativeNote / properties / color / title
```
Removed value: -"Color"
```
- removedOutput schema / $defs / CreativeNote / properties / duration_beats / title
```
Removed value: -"Duration Beats"
```
- removedOutput schema / $defs / CreativeNote / properties / muted / title
```
Removed value: -"Muted"
```
- removedOutput schema / $defs / CreativeNote / properties / pan / title
```
Removed value: -"Pan"
```
- removedOutput schema / $defs / CreativeNote / properties / pitch / title
```
Removed value: -"Pitch"
```
- removedOutput schema / $defs / CreativeNote / properties / pitch_offset_tenths / title
```
Removed value: -"Pitch Offset Tenths"
```
- removedOutput schema / $defs / CreativeNote / properties / portamento / title
```
Removed value: -"Portamento"
```
- removedOutput schema / $defs / CreativeNote / properties / release / title
```
Removed value: -"Release"
```
- removedOutput schema / $defs / CreativeNote / properties / selected / title
```
Removed value: -"Selected"
```
- removedOutput schema / $defs / CreativeNote / properties / slide / title
```
Removed value: -"Slide"
```
- removedOutput schema / $defs / CreativeNote / properties / start_beats / title
```
Removed value: -"Start Beats"
```
- removedOutput schema / $defs / CreativeNote / properties / velocity / title
```
Removed value: -"Velocity"
```
- removedOutput schema / $defs / CreativeNote / title
```
Removed value: -"CreativeNote"
```
- removedOutput schema / $defs / NoteSequence / properties / duration_beats / title
```
Removed value: -"Duration Beats"
```
- removedOutput schema / $defs / NoteSequence / properties / engine_version / title
```
Removed value: -"Engine Version"
```
- removedOutput schema / $defs / NoteSequence / properties / generator / title
```
Removed value: -"Generator"
```
- removedOutput schema / $defs / NoteSequence / properties / mutations_applied / title
```
Removed value: -"Mutations Applied"
```
- removedOutput schema / $defs / NoteSequence / properties / name / title
```
Removed value: -"Name"
```
- removedOutput schema / $defs / NoteSequence / properties / note_count / title
```
Removed value: -"Note Count"
```
- removedOutput schema / $defs / NoteSequence / properties / note_digest_sha256 / title
```
Removed value: -"Note Digest Sha256"
```
- removedOutput schema / $defs / NoteSequence / properties / notes / title
```
Removed value: -"Notes"
```
- removedOutput schema / $defs / NoteSequence / properties / pitch_collection / title
```
Removed value: -"Pitch Collection"
```
- removedOutput schema / $defs / NoteSequence / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / $defs / NoteSequence / properties / seed / title
```
Removed value: -"Seed"
```
- removedOutput schema / $defs / NoteSequence / properties / tempo_bpm / title
```
Removed value: -"Tempo Bpm"
```
- removedOutput schema / $defs / NoteSequence / properties / time_signature_denominator / title
```
Removed value: -"Time Signature Denominator"
```
- removedOutput schema / $defs / NoteSequence / properties / time_signature_numerator / title
```
Removed value: -"Time Signature Numerator"
```
- removedOutput schema / $defs / NoteSequence / properties / warnings / title
```
Removed value: -"Warnings"
```
- removedOutput schema / $defs / NoteSequence / title
```
Removed value: -"NoteSequence"
```
- removedOutput schema / properties / analyzed_duration_seconds / title
```
Removed value: -"Analyzed Duration Seconds"
```
- removedOutput schema / properties / fmax_hz / title
```
Removed value: -"Fmax Hz"
```
- removedOutput schema / properties / fmin_hz / title
```
Removed value: -"Fmin Hz"
```
- removedOutput schema / properties / frame_hop_seconds / title
```
Removed value: -"Frame Hop Seconds"
```
- removedOutput schema / properties / limitations / title
```
Removed value: -"Limitations"
```
- removedOutput schema / properties / median_pitch_confidence / title
```
Removed value: -"Median Pitch Confidence"
```
- removedOutput schema / properties / method / title
```
Removed value: -"Method"
```
- removedOutput schema / properties / mutations_applied / title
```
Removed value: -"Mutations Applied"
```
- removedOutput schema / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / properties / source_path / title
```
Removed value: -"Source Path"
```
- removedOutput schema / properties / source_sha256 / title
```
Removed value: -"Source Sha256"
```
- removedOutput schema / properties / tempo_bpm_used / title
```
Removed value: -"Tempo Bpm Used"
```
- removedOutput schema / properties / tempo_source / title
```
Removed value: -"Tempo Source"
```
- removedOutput schema / properties / transcribed_at / title
```
Removed value: -"Transcribed At"
```
- removedOutput schema / properties / voiced_frame_share / title
```
Removed value: -"Voiced Frame Share"
```
- removedOutput schema / title
```
Removed value: -"MelodyTranscription"
```
Changed8 schema fields changedv11.0.1Oct 3, 2026
- removedInput schema / properties / fmax_hz / title
```
Removed value: -"Fmax Hz"
```
- removedInput schema / properties / fmin_hz / title
```
Removed value: -"Fmin Hz"
```
- removedInput schema / properties / max_seconds / title
```
Removed value: -"Max Seconds"
```
- removedInput schema / properties / minimum_note_seconds / title
```
Removed value: -"Minimum Note Seconds"
```
- removedInput schema / properties / path / title
```
Removed value: -"Path"
```
- removedInput schema / properties / quantize_grid_beats / title
```
Removed value: -"Quantize Grid Beats"
```
- removedInput schema / properties / tempo_bpm / title
```
Removed value: -"Tempo Bpm"
```
- removedInput schema / title
```
Removed value: -"audio_transcribe_melodyArguments"
```
First observedv10.0.0Sep 14, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description usefully reinforces 'Reads the file only' plus a quality caveat (polyphonic material transcribes poorly). It stops short of noting runtime/rate characteristics or how failure modes look, but with annotations carrying the safety profile this is solid added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then constraints, then downstream routing; every sentence earns its place. Slight redundancy between 'monophonic recording (a sung or played line)' and the closing 'give it one isolated line', which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers input prerequisites, scope limits and the next step in the workflow. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including fmin/fmax, tempo_bpm, quantize_grid_beats and minimum_note_seconds is already documented in the schema. The description only alludes to beat-positioning ('note sequence in beats'), adding no syntax or format detail beyond the schema — baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Transcribe a monophonic recording ... into notes') and immediately scopes it against siblings like audio_analyze_file and audio_estimate_tempo_and_key by naming the input constraint (one isolated line) and the output form (note sequence in beats). An agent can tell what this does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use it ('Chords and full mixes transcribe poorly; give it one isolated line') and routes the agent downstream to piano_roll_write_notes or compose_export_midi, which makes the place in the workflow unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server