MCP Audio Studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUDIO_STUDIO_DATA | No | Path to a JSON file for persisting project revisions. | |
| MCP_AUDIO_STUDIO_TLS_KEY | No | Path to TLS private key file for trusted HTTPS mode. | |
| MCP_AUDIO_STUDIO_TLS_CERT | No | Path to TLS certificate file for trusted HTTPS mode. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| studio_uiA | Open the complete interactive DAW. Use this when the user wants to see or edit the studio visually. |
| get_projectA | Return the authoritative DAW project, including transport, tracks, steps, clips, mixer, effects, plugins, EQ, and automation. |
| new_projectA | Create a fresh demo-ready audio project, replacing the current project. |
| set_projectA | Rename the current project. |
| set_transportC | Change playback, recording, tempo, time signature, swing, metronome, position, and loop settings. |
| add_trackB | Add an instrument or audio track linked to a built-in, sampler, WAM, or VST3 instrument slot. |
| update_trackB | Update track name, color, type, instrument, preset, oscillator, or instrument parameters. |
| remove_trackA | Remove a track and its notes, clips, mixer channel, effects, plugins, and related automation. |
| set_stepsA | Edit step-sequencer or piano-roll notes. Each update can toggle a step and set MIDI note, velocity, and gate length. |
| add_audio_clipB | Place an audio file on a track. Pass a data URL for bundled audio or a source URL for a remotely hosted file. |
| update_audio_clipA | Move, trim, rename, or change the gain of an audio clip. |
| remove_audio_clipA | Remove an audio clip from a track. |
| set_mixerA | Set volume, panning, mute, solo, and send levels for a track or the master channel. |
| set_equalizerB | Set the four-band EQ gains in dB for a track. |
| add_effectA | Add a filter, delay, reverb, distortion, compressor, chorus, or limiter to a track effects chain. |
| update_effectA | Enable, bypass, rename, mix, or change parameters on an effect slot. |
| remove_effectA | Remove an effect from a track effects chain. |
| add_pluginC | Add a built-in, Web Audio Module (WAM), or VST3 plugin slot. VST3 slots expose parameters and state for a native bridge. |
| update_pluginA | Enable, bypass, rename, change parameters, or store opaque plugin state for a plugin slot. |
| remove_pluginB | Remove a plugin slot from a track. |
| upsert_automationA | Create or update an automation lane for master/track volume, pan, effect, plugin, or instrument parameters. |
| remove_automationC | Remove an automation lane. |
| export_projectB | Export the complete project as portable JSON. |
| import_projectA | Replace the current project from an exported project JSON document. |
| render_audioA | Offline-render the current project to a stereo 16-bit WAV file and return playable audio. |
| get_renderA | Retrieve a recent rendered WAV file by render ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Audio Studio UI | Complete interactive Audio Studio DAW interface. |
TDQS
Scored across 26 tools
Each tool targets a distinct resource and action: tracks, audio clips, effects, plugins, automation, steps, mixer, EQ, transport, and project. Even closely related tools like add_effect and add_plugin are clearly differentiated by description (built-in effects vs. plugin formats).
Tool names overwhelmingly follow a verb_noun pattern (add_track, update_track, remove_track, set_mixer, render_audio). There is one minor deviation (studio_ui), but it is clearly a UI action and does not disrupt the overall consistency.
With 26 tools, the server is above the typical range and borders on excessive. However, the comprehensive scope of a DAW (tracks, clips, effects, plugins, automation, mixing, transport, rendering) makes the high count defensible, though it remains on the heavy side.
The tool surface covers project lifecycle, track management, clip editing, effects/plugins, automation, step sequencing, mixer/EQ, transport, and rendering. Minor gaps exist, such as no dedicated getter for individual tracks/clips (get_project returns everything), but these are not critical and do not impede core workflows.