easyeffects-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EASYEFFECTS_SOCKET | No | Path to the Easy Effects control socket, in case it's in an unusual place. Set it in your MCP client's env block. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusB | Overview: global bypass, mic monitoring, audio sharing, devices, last loaded presets and active plugin chains. |
| set_global_bypassA | Enable (true) or disable (false) the global bypass. Bypass on = all effects off. |
| set_microphone_monitoringB | Turn microphone monitoring (hear your processed mic) on or off. |
| set_audio_sharingB | Turn audio sharing (route processed output to the virtual source) on or off. |
| windowB | Show or hide the Easy Effects window. |
| list_presetsB | List saved input and output presets, plus the last loaded one for each. |
| load_presetC | Load a saved preset into the input or output pipeline. |
| read_presetC | Return the JSON contents of a saved preset file. |
| save_presetA | Write a preset JSON file (same format read_preset returns; top-level key must be the pipeline name). Tip: read an existing preset first and modify it, rather than writing one from scratch. |
| get_plugin_propertyA | Read one property of an active plugin (see get_status for the plugin chain). |
| set_plugin_propertyB | Set one property of an active plugin. Returns the value read back from Easy Effects. |
| bypass_pluginC | Bypass (disable) or re-enable a single plugin in the chain. |
| get_equalizerB | Read the parametric equalizer: gains, mode and every active band for both channels. |
| set_equalizer_bandC | Change one equalizer band. Only the fields you pass are changed. Applies to both channels by default. |
| apply_parametric_eqB | Replace the whole equalizer with a list of bands (e.g. from an AutoEQ ParametricEQ.txt), applied to both channels. Requires an equalizer plugin in the chain. |
| list_plugin_instancesB | Active plugins in a pipeline, in processing order, with their bypass state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools target clearly distinct actions (e.g., set_equalizer_band vs. apply_parametric_eq vs. get_equalizer), and global vs. plugin-specific bypass are separated. Minor overlap exists between the generic set_plugin_property and the specialized equalizer tools, but descriptions help disambiguate.
Nearly all tools follow a verb_noun pattern (get_status, set_global_bypass, list_presets, save_preset, etc.). The outlier is 'window', which lacks a verb, but otherwise naming is predictable.
With 16 tools, the set sits at the borderline of being heavy for the apparent scope. While no tool seems entirely redundant, the count is above the ideal 3–15 range and some generic property tools could potentially be consolidated.
Core operations for equalizer, presets, plugins, and toggles are present, but notable gaps exist: no delete_preset, no add/remove plugin, and no reset-to-flat equalizer or device selection. These gaps may cause agent workarounds.