Skip to main content
Glama

add_fx

Add an FX plugin, including VSTi instruments and VST/AU effects, to a specified track by providing the track index and the exact plugin name as shown in REAPER's FX browser.

Instructions

Add an FX plugin to a track. Works for both instruments (VSTi) and effects (VST/AU). Use the exact plugin name as shown in REAPER's FX browser. Built-in Cockos plugins: ReaEQ, ReaComp, ReaDelay, ReaVerb, ReaLimit, ReaSynth, ReaSamplOmatic5000, ReaTune, ReaGate, ReaFIR, ReaXcomp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_nameYes

Implementation Reference

  • The add_fx handler function: adds an FX plugin to a track by name. Uses reapy's track.add_fx() to find and add the plugin. Returns success with fx_index, name, and n_params, or an error message on failure.
    def add_fx(track_index: int, fx_name: str) -> dict:
        """
        Add an FX plugin to a track. Works for both instruments (VSTi) and effects (VST/AU).
        Use the exact plugin name as shown in REAPER's FX browser.
        Built-in Cockos plugins: ReaEQ, ReaComp, ReaDelay, ReaVerb, ReaLimit, ReaSynth,
        ReaSamplOmatic5000, ReaTune, ReaGate, ReaFIR, ReaXcomp.
        """
        try:
            project = get_project()
            track = project.tracks[track_index]
            fx_index = track.add_fx(fx_name)
            if fx_index < 0:
                return {"success": False, "error": f"Plugin not found: '{fx_name}'"}
            fx = track.fxs[fx_index]
            return {
                "success": True,
                "fx_index": fx_index,
                "name": fx.name,
                "n_params": fx.n_params,
                "track_index": track_index,
            }
        except Exception as e:
            logger.error(f"add_fx failed: {e}")
            return {"success": False, "error": str(e)}
  • The function signature defines the schema: parameters track_index (int) and fx_name (str), returns dict.
    def add_fx(track_index: int, fx_name: str) -> dict:
  • The tool is registered via the @mcp.tool() decorator inside register_tools(mcp), which is called from server.py.
    def register_tools(mcp):
    
        @mcp.tool()
  • Import and invocation of fx_tools.register_tools (aliased as _reg_fx) in the main server module.
    from reaper_mcp.fx_tools import register_tools as _reg_fx
    from reaper_mcp.audio_tools import register_tools as _reg_audio
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
    from reaper_mcp.render_tools import register_tools as _reg_render
    from reaper_mcp.mastering_tools import register_tools as _reg_mastering
    from reaper_mcp.analysis_tools import register_tools as _reg_analysis
    
    _reg_project(mcp)
    _reg_track(mcp)
    _reg_midi(mcp)
    _reg_fx(mcp)
  • The get_project helper function used by add_fx to ensure REAPER connection and get the active project.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior3/5

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

Discloses that it works for both instruments and effects, but lacks details on whether the FX is added to the end of the chain, permissions needed, or any side effects. Without annotations, the description carries full burden and provides only basic behavioral info.

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?

Three front-loaded sentences, no fluff. The list of built-in plugins is a helpful addition without being verbose.

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

Completeness4/5

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

Covers core functionality adequately given the simplicity of the tool and lack of output schema, but could mention default positioning in the FX chain and clarify track_index indexing.

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?

The description adds meaning for 'fx_name' by specifying exact naming format and examples, but does not explain 'track_index' (e.g., 0-indexed or 1-indexed). With 0% schema coverage, description partially compensates.

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?

Clearly states the action 'Add an FX plugin to a track' and distinguishes from sibling 'add_master_fx' by specifying 'to a track'.

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

Usage Guidelines4/5

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

Provides explicit guidance on using exact plugin names as in the browser and lists common built-in plugins, but does not clearly differentiate when to use this tool vs alternatives like 'add_master_fx' or 'bypass_fx'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bonfire-audio/reaper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server