PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

audio_analyze_file

Read-onlyIdempotent

Analyze an exported audio file to measure loudness, peaks, spectrum, dynamics, and stereo image, with optional pitch detection for stems.

Instructions

Measure one rendered file's loudness, peaks, spectrum, dynamics, and stereo image.

Reads the file only; FL's live output is not available. Returns integrated
and short-term loudness (LUFS), loudness range, sample and true peak,
spectral band balance, dynamics, stereo correlation and mono compatibility,
and optional pitch. Use audio_diagnose_mix for a pass/fail mix diagnosis,
audio_compare_files against a reference, and audio_list_recent_bounces to
find the user's latest export.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Absolute path to an existing audio file exported from FL Studio.
`max_seconds`	No	Optional shorter analysis bound in seconds; the default reads up to 600.
`include_pitch`	No	Also run the monophonic pitch tracker; useful for a lead vocal stem, unreliable for a full mix.

Output Schema

TableJSON Schema

Name	Required	Default
`file`	Yes
`pitch`	No
`stereo`	Yes
`dynamics`	Yes
`loudness`	Yes
`spectrum`	Yes
`confidence`	Yes
`limitations`	Yes
`measured_at`	Yes
`interpretation`	No	measurements_only
`schema_version`	No	1.0
`analyzer_version`	Yes
`analyzer_versions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed94 schema fields changedv11.0.2Oct 5, 2026
- changedInput schema / properties / path / description
```
Previous value: -"Absolute path to an existing audio file bounced from FL Studio."New value: +"Absolute path to an existing audio file exported from FL Studio."
```
- removedOutput schema / $defs / AnalyzerVersions / properties / alignment / title
```
Removed value: -"Alignment"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / dynamics / title
```
Removed value: -"Dynamics"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / integrated_loudness / title
```
Removed value: -"Integrated Loudness"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / loudness_matching / title
```
Removed value: -"Loudness Matching"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / pitch / title
```
Removed value: -"Pitch"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / spectrum / title
```
Removed value: -"Spectrum"
```
- removedOutput schema / $defs / AnalyzerVersions / properties / true_peak / title
```
Removed value: -"True Peak"
```
- removedOutput schema / $defs / AnalyzerVersions / title
```
Removed value: -"AnalyzerVersions"
```
- removedOutput schema / $defs / AudioFileDescription / properties / analyzed_frames / title
```
Removed value: -"Analyzed Frames"
```
- removedOutput schema / $defs / AudioFileDescription / properties / channels / title
```
Removed value: -"Channels"
```
- removedOutput schema / $defs / AudioFileDescription / properties / duration_sec / title
```
Removed value: -"Duration Sec"
```
- removedOutput schema / $defs / AudioFileDescription / properties / format / title
```
Removed value: -"Format"
```
- removedOutput schema / $defs / AudioFileDescription / properties / max_seconds / title
```
Removed value: -"Max Seconds"
```
- removedOutput schema / $defs / AudioFileDescription / properties / path / title
```
Removed value: -"Path"
```
- removedOutput schema / $defs / AudioFileDescription / properties / sample_rate / title
```
Removed value: -"Sample Rate"
```
- removedOutput schema / $defs / AudioFileDescription / properties / sha256 / title
```
Removed value: -"Sha256"
```
- removedOutput schema / $defs / AudioFileDescription / properties / source_duration_sec / title
```
Removed value: -"Source Duration Sec"
```
- removedOutput schema / $defs / AudioFileDescription / properties / source_frames / title
```
Removed value: -"Source Frames"
```
- removedOutput schema / $defs / AudioFileDescription / properties / subtype / title
```
Removed value: -"Subtype"
```
- removedOutput schema / $defs / AudioFileDescription / properties / truncated / title
```
Removed value: -"Truncated"
```
- removedOutput schema / $defs / AudioFileDescription / properties / truncated_by / title
```
Removed value: -"Truncated By"
```
- removedOutput schema / $defs / AudioFileDescription / title
```
Removed value: -"AudioFileDescription"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / dynamic_spread_db / title
```
Removed value: -"Dynamic Spread Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / noise_floor_db / title
```
Removed value: -"Noise Floor Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / note / title
```
Removed value: -"Note"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / rms_median_db / title
```
Removed value: -"Rms Median Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / rms_p10_db / title
```
Removed value: -"Rms P10 Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / rms_p90_db / title
```
Removed value: -"Rms P90 Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / rms_p95_db / title
```
Removed value: -"Rms P95 Db"
```
- removedOutput schema / $defs / DynamicsMeasurements / properties / silence_share / title
```
Removed value: -"Silence Share"
```
- removedOutput schema / $defs / DynamicsMeasurements / title
```
Removed value: -"DynamicsMeasurements"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / channel_count / title
```
Removed value: -"Channel Count"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / clipped_frames / title
```
Removed value: -"Clipped Frames"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / clipped_samples / title
```
Removed value: -"Clipped Samples"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / clipped_samples_per_channel / title
```
Removed value: -"Clipped Samples Per Channel"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / crest_factor_db / title
```
Removed value: -"Crest Factor Db"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / dc_offset / title
```
Removed value: -"Dc Offset"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / dc_offset_per_channel / title
```
Removed value: -"Dc Offset Per Channel"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / headroom_to_0dbtp / title
```
Removed value: -"Headroom To 0Dbtp"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / loudness_range_lu / title
```
Removed value: -"Loudness Range Lu"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / lufs_integrated / title
```
Removed value: -"Lufs Integrated"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / lufs_short_term_max / title
```
Removed value: -"Lufs Short Term Max"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / lufs_short_term_min / title
```
Removed value: -"Lufs Short Term Min"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / rms_db / title
```
Removed value: -"Rms Db"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / rms_db_per_channel / title
```
Removed value: -"Rms Db Per Channel"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / sample_peak_db / title
```
Removed value: -"Sample Peak Db"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / sample_peak_db_per_channel / title
```
Removed value: -"Sample Peak Db Per Channel"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / true_peak_dbtp / title
```
Removed value: -"True Peak Dbtp"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / true_peak_dbtp_per_channel / title
```
Removed value: -"True Peak Dbtp Per Channel"
```
- removedOutput schema / $defs / LoudnessMeasurements / properties / true_peak_method / title
```
Removed value: -"True Peak Method"
```
- removedOutput schema / $defs / LoudnessMeasurements / title
```
Removed value: -"LoudnessMeasurements"
```
- removedOutput schema / $defs / MeasurementConfidence / properties / basis / title
```
Removed value: -"Basis"
```
- removedOutput schema / $defs / MeasurementConfidence / properties / level / title
```
Removed value: -"Level"
```
- removedOutput schema / $defs / MeasurementConfidence / properties / scope / title
```
Removed value: -"Scope"
```
- removedOutput schema / $defs / MeasurementConfidence / properties / score / title
```
Removed value: -"Score"
```
- removedOutput schema / $defs / MeasurementConfidence / title
```
Removed value: -"MeasurementConfidence"
```
- removedOutput schema / $defs / PitchMeasurements / properties / cents_off_mean_abs / title
```
Removed value: -"Cents Off Mean Abs"
```
- removedOutput schema / $defs / PitchMeasurements / properties / cents_off_p90 / title
```
Removed value: -"Cents Off P90"
```
- removedOutput schema / $defs / PitchMeasurements / properties / in_tune_share_within_20c / title
```
Removed value: -"In Tune Share Within 20C"
```
- removedOutput schema / $defs / PitchMeasurements / properties / in_tune_share_within_50c / title
```
Removed value: -"In Tune Share Within 50C"
```
- removedOutput schema / $defs / PitchMeasurements / properties / median_cents_off / title
```
Removed value: -"Median Cents Off"
```
- removedOutput schema / $defs / PitchMeasurements / properties / median_hz / title
```
Removed value: -"Median Hz"
```
- removedOutput schema / $defs / PitchMeasurements / properties / median_note / title
```
Removed value: -"Median Note"
```
- removedOutput schema / $defs / PitchMeasurements / properties / note / title
```
Removed value: -"Note"
```
- removedOutput schema / $defs / PitchMeasurements / properties / pitch_jitter_cents / title
```
Removed value: -"Pitch Jitter Cents"
```
- removedOutput schema / $defs / PitchMeasurements / properties / range_high_note / title
```
Removed value: -"Range High Note"
```
- removedOutput schema / $defs / PitchMeasurements / properties / range_low_note / title
```
Removed value: -"Range Low Note"
```
- removedOutput schema / $defs / PitchMeasurements / properties / voiced_share / title
```
Removed value: -"Voiced Share"
```
- removedOutput schema / $defs / PitchMeasurements / title
```
Removed value: -"PitchMeasurements"
```
- removedOutput schema / $defs / SpectralBand / properties / energy_share / title
```
Removed value: -"Energy Share"
```
- removedOutput schema / $defs / SpectralBand / properties / level_db / title
```
Removed value: -"Level Db"
```
- removedOutput schema / $defs / SpectralBand / properties / range_hz / title
```
Removed value: -"Range Hz"
```
- removedOutput schema / $defs / SpectralBand / title
```
Removed value: -"SpectralBand"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / bands / title
```
Removed value: -"Bands"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / dominant_hz / title
```
Removed value: -"Dominant Hz"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / sibilance_peak_hz / title
```
Removed value: -"Sibilance Peak Hz"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / sibilance_ratio / title
```
Removed value: -"Sibilance Ratio"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / spectral_centroid_hz / title
```
Removed value: -"Spectral Centroid Hz"
```
- removedOutput schema / $defs / SpectrumMeasurements / properties / sub_40hz_share / title
```
Removed value: -"Sub 40Hz Share"
```
- removedOutput schema / $defs / SpectrumMeasurements / title
```
Removed value: -"SpectrumMeasurements"
```
- removedOutput schema / $defs / StereoMeasurements / properties / balance_db / title
```
Removed value: -"Balance Db"
```
- removedOutput schema / $defs / StereoMeasurements / properties / channels / title
```
Removed value: -"Channels"
```
- removedOutput schema / $defs / StereoMeasurements / properties / correlation / title
```
Removed value: -"Correlation"
```
- removedOutput schema / $defs / StereoMeasurements / properties / mid_side_ratio / title
```
Removed value: -"Mid Side Ratio"
```
- removedOutput schema / $defs / StereoMeasurements / properties / mono_compatible / title
```
Removed value: -"Mono Compatible"
```
- removedOutput schema / $defs / StereoMeasurements / properties / note / title
```
Removed value: -"Note"
```
- removedOutput schema / $defs / StereoMeasurements / title
```
Removed value: -"StereoMeasurements"
```
- removedOutput schema / properties / analyzer_version / title
```
Removed value: -"Analyzer Version"
```
- removedOutput schema / properties / interpretation / title
```
Removed value: -"Interpretation"
```
- removedOutput schema / properties / limitations / title
```
Removed value: -"Limitations"
```
- removedOutput schema / properties / measured_at / title
```
Removed value: -"Measured At"
```
- removedOutput schema / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / title
```
Removed value: -"AudioFileAnalysis"
```
Changed4 schema fields changedv11.0.1Oct 3, 2026
- removedInput schema / properties / include_pitch / title
```
Removed value: -"Include Pitch"
```
- removedInput schema / properties / max_seconds / title
```
Removed value: -"Max Seconds"
```
- removedInput schema / properties / path / title
```
Removed value: -"Path"
```
- removedInput schema / title
```
Removed value: -"audio_analyze_fileArguments"
```
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 read-only, idempotent, non-destructive behavior, but the description adds meaningful context beyond them: it clarifies that only a rendered file is analyzed and live FL output is inaccessible. It also enumerates outputs at a high level, though it does not discuss rate limits or authentication, so it stops short of full behavioral disclosure.

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?

The description is front-loaded with the core purpose in the first sentence, then adds useful routing and return-context sentences. The return-value list is somewhat lengthy given that an output schema exists, but it still helps an agent understand the tool's scope without wasting words.

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?

Given a read-only measurement tool with an output schema and safety annotations, the description supplies what an agent needs: purpose, a limitation (no live output), and explicit alternatives. Return values are covered by the output schema, so the description is complete without duplicating them in detail.

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 all three parameters are fully documented in the input schema. The description only alludes to 'optional pitch' and does not add syntax, format, or constraint details beyond what the schema already provides, making the baseline 3 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?

First sentence names a specific verb (Measure) and concrete resource (one rendered file) plus the measured attributes, so an agent immediately knows what the tool does. The later sentences explicitly name the sibling tools it differs from (audio_diagnose_mix, audio_compare_files, audio_list_recent_bounces), enabling correct selection without opening schemas.

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?

The description states a clear operating constraint (reads the file only; FL's live output is not available) and explicitly routes the agent to alternatives for diagnosis, reference comparison, and finding the latest export. This provides both when-to-use and when-to-use-another-tool guidance.

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

Deploy Server