PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

plugin_load

Destructive

Add an instrument or mixer effect from FL Studio's Add menu on macOS. Returns the new channel or effect slot for preset selection or parameter changes; requires write mode.

Instructions

Add one instrument (new channel) or mixer effect from FL's Add menu (macOS).

Use an exact name from plugin_list_available. Requires write mode; an
effect load first selects its mixer track. Returns the new channel or
effect slot as a target for plugin_select_preset or plugin_set_parameter.
If the outcome is unknown, inspect plugin_list_loaded before trying again.
Windows insertion is not implemented. Does not save the project.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Exact Add-menu name, kind (instrument or effect), and for effects the mixer track_index.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`request`	Yes
`verified`	No
`warnings`	No
`menu_path`	No
`dispatched`	No
`observed_at`	Yes
`loaded_plugin`	No
`project_saved`	No
`undo_point_created`	No
`session_fingerprint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds substantive context beyond them: the write-mode prerequisite, the side effect of an effect load selecting its mixer track, that the project is not saved, and the recovery path when the outcome is uncertain.

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

Conciseness5/5

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

Five short sentences, each carrying a distinct operational fact, with the core action and its platform scope front-loaded before prerequisites and recovery guidance.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the returned channel/effect slot as a target for plugin_select_preset and plugin_set_parameter. Platform limits, auth mode, side effects, and failure recovery are all covered.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the name must be an exact Add-menu entry sourced from plugin_list_available, and track_index is implied to matter for effect loads. It stops short of explaining allow_master, timeout_seconds, or session_fingerprint.

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 (add/load) plus the two distinct resources it can create (instrument channel or mixer effect) and scopes it to FL's Add menu on macOS. An agent can distinguish it from plugin_list_available and plugin_list_loaded immediately.

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 routes the agent: use an exact name from plugin_list_available, requires write mode, effects first select their mixer track, and if the outcome is unknown inspect plugin_list_loaded before retrying. Also states the negative condition that Windows insertion is not implemented.

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

Deploy Server