FmodStudioMCP
This server gives an MCP-compatible AI assistant full control over FMOD Studio game-audio projects by executing safe, validated tools over FMOD's built-in scripting terminal.
Project management: get info, save/save-all, build banks (optionally scoped), check unsaved changes, validate project.
Events: create/delete/rename/list/lookup, move into folders, add tracks, set max voices, scrub timeline cursor.
Auditioning: play, stop, pause, keyoff, return-to-start, and query playback status of event instances.
Markers & transitions: add/rename/move/delete named markers, loop regions, sustain points, transition markers/regions, and crossfaded transition timelines.
Sound & audio: import audio assets, create/place Single/Multi/Programmer/Scatterer/Event instruments, assign audio files and owners, inspect instrument state.
Parameters: add all parameter types, set initial values, enumeration labels, list event parameters.
Automation: add/list curves and points for volume/pitch/gain driven by parameters or timeline.
Banks: create/rename/delete banks, assign/remove/list events in banks.
Mixer & routing: create/rename/delete/route mixer groups, set volumes, add/list effects, control master bus, create sends/returns, manage VCAs and assignments.
Snapshots: create/list/info/rename/delete mixer snapshots and bind groups to them.
Folders & workspace: create/list folders, inspect workspace roots, current browser/editor selection, navigate the editor.
Utility: generic lookup/list/delete/isValid, object introspection via dump, and project validation.
Provides tools for authoring game audio in FMOD Studio, including creating events, importing audio, managing parameters, routing mixer buses, assigning banks, and building the project.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FmodStudioMCP Create an event called Player/Footsteps with a footstep.wav loop"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FmodStudioMCP connects any MCP-compatible AI assistant to FMOD Studio, the game-audio middleware, and gives it full control over the authoring tool. Talk to your AI and it creates events, imports audio, builds parameter cultures, routes mixer buses, assigns banks, and builds your project — while you watch the editor apply every change live.
It runs over FMOD Studio's built-in JavaScript scripting terminal (TCP, port 3663), so — like its sibling ReaperMCP — there is no plugin, no cloud, nothing to install inside the tool: FMOD Studio ships the bridge. The MCP server is the only new piece, and it talks to a stock FMOD Studio install.
If this is useful to you, a star helps other people find it.
Works With
Claude Desktop, Claude Code, Cursor, or any MCP-compatible client
Quick Start
1. Get FmodStudioMCP
Install directly:
pip install xdarkzx-fmod-studio-mcpor clone and pip install -e . for development (see CONTRIBUTING.md).
2. Enable FMOD Studio's Script Server (one time)
The scripting terminal is disabled by default, and opening the console with Ctrl+0 is not enough — that only shows output.
Launch FMOD Studio and open your project (
.fspro).Edit → Preferences…(Windows) orFMOD Studio → Preferences…(macOS).On the Interface tab, tick Enable Script Server (requires restart).
Quit and relaunch FMOD Studio, then reopen the project. The port is
3663by default.
Confirmed it's listening? Check the newest log under
%LOCALAPPDATA%\FMOD Studio\Logs\for[Scripting] ScriptServer started on 127.0.0.1 (3663).
3. Register the server with your MCP client
{
"mcpServers": {
"fmod-studio": {
"command": "fmod-studio-mcp"
}
}
}fmod-studio-mcp reads FMOD_STUDIO_HOST / FMOD_STUDIO_PORT (defaults 127.0.0.1:3663) if your setup differs.
4. Start authoring
"List every event in the project"
"Create an event called 'Player/Footsteps' with a SingleSound loop of footsteps.wav"
"Add a 'Fear' User parameter to it, range 0-1, initial 0"
"Assign it to the Master bank and build the project"FMOD Studio must be running with a project open. The bridge cannot launch Studio for you, and the Script Server only binds once a project is open.
Related MCP server: fmod-mcp
Features
Curated tool surface (not generated)
Unlike auto-generated "one tool per API member" servers, every tool here is hand-shaped around the real authoring workflow. 90+ tools in 13 modules —
Module | Tools | Highlights |
Project | 5 | Get info, save, save-all, build banks (optionally scoped to specific banks/platforms), modified-check |
Events | 11 | Create/delete/list/lookup, rename, folders, group tracks, maxVoices, timeline scrub |
Audition | 6 | Play/stop/pause/keyoff, return-to-start, playback status — hear the result, don't just read the tree |
Markers | 11 | Marker tracks, named markers, loop regions, sustain points, transition markers/regions, list/rename/reposition/delete |
Sounds | 8 | Import audio assets, place Single/Multi/Programmer/Scatterer/Event instruments, wire audioFile + owners |
Parameters | 4 | Add game parameters (all 6 types), enumeration labels, initial values, list |
Banks | 8 | Create/rename/delete, assign/remove events, list membership |
Automation | 3 | Parameter/timeline-driven curves — the heart of evolving/interactive music |
Snapshots | 6 | Mixer state presets the game activates as blendable layers |
Mixer | 17 | Groups + routing, dB volume, effect chains (24 effects), master bus, VCAs, per-event sends/returns |
Folders | 2 | Create hierarchies, list browser tree |
Workspace | 4 | Browser/editor selection, navigate-to, roots |
Utility | 6 | Generic lookup/list/delete/isValid, debug dump, project validation |
Typed, safe by default
Every command is a named, schema-validated operation — no arbitrary-script escape hatch (same policy as ReaperMCP).
Values are validated before they reach Studio (names, dB ranges, type whitelists, audio file paths/extensions).
Params travel as inert JSON literals into a self-trapping JS wrapper — a hostile string can't break out of its quotes or reach the command body.
Results are capped (
MAX_OBJECTS_READ, etc.) so a busy project can't flood your model's context window.
Profile-trimmable tool surface
Smaller/cheaper models truncate tool lists. Set FMOD_STUDIO_MCP_PROFILE in your client's server config to pick a workflow-specific subset:
Profile | For |
| All 13 modules |
| Building/editing events, sounds, parameters, audition, markers |
| Mixer structure, routing, effects, audition, markers |
| Bank management + build plumbing |
| Read the project, verify the bridge |
Production-grade plumbing, same as ReaperMCP
TCP bridge with read-until-idle framing + typed connection/timeout errors (never a silent hang).
Cross-process file mutex so multiple MCP clients can share one Studio without their evals interleaving.
Command history archive (30-day retention) for after-the-fact debugging.
Startup UTF-8 stdio fix and a self-retiring parent watchdog — battle-tested client behaviour inherited from ReaperMCP.
Architecture
┌──────────────┐ stdio ┌──────────────┐ TCP 3663 ┌──────────────┐
│ MCP Client │◄──────────►│ FmodStudioMCP│◄──────────────►│ FMOD Studio │
│(AI assistant)│ (JSON-RPC) │ FastMCP │ (JS eval) │ (JS terminal)│
└──────────────┘ └──────────────┘ └──────────────┘The Python server wraps every tool's command body in a self-evaluating, error-trapping JavaScript IIFE, sends it to the Script Server, and parses the string reply back into a structured result. No cloud. Nothing leaves your machine — Studio and the AI talk over localhost.
Full details — framing, wrapping, safety limits, lifecycle — in docs/ARCHITECTURE.md.
Troubleshooting
Problem | Fix |
"Cannot reach FMOD Studio's scripting terminal" | Script Server isn't enabled. Preferences → Interface → tick Enable Script Server → restart FMOD Studio, then open a project. |
Enabled but nothing on 3663 | A project must be open before the server binds. Check |
Port conflict | Set the same value in FMOD Studio's Preferences and |
Claude Desktop doesn't see it | Restart Claude Desktop after editing its config file. |
"command not found: fmod-studio-mcp" | Reinstall with |
Development
pip install -e ".[dev]"
pytest tests/ -x -q
ruff check .Adding a tool
Add a module in
fmod_mcp/tools/(or extend an existing one).Export
register(mcp: FastMCP).Define tools with
@mcp.tool(), using theclient.execute("js body", **params)helper.Add the module name to
_EXPECTED_MODULESintool_registry.py.Every new tool is automatically exercised by the test harness in
tests/test_tools_registration.py.
See CONTRIBUTING.md for full guidelines.
License
Apache License 2.0 — see LICENSE for details.
Built by Daniel Hodgetts (@xDarkzx).
Need a custom tool, plugin, or integration built like this? Open an issue.
Available Tools
92 toolsaudio_assetsA
List imported audio assets in the project (capped).
Inputs: no named parameters.
audio_importA
Import an audio file into the project as a reusable asset.
Returns the asset's {guid} so it can be assigned to an instrument. Long operation — asset files are copied into the project.
Args: file_path: Absolute path to a .wav/.aiff/.flac/.mp3/.ogg file.
Inputs: file_path (required).
automation_addA
Add one point to an existing curve (or start a new one). Same target/driver/property reuses the matching curve.
Args: target: Mixer group/bus/VCA/event mixer group {guid}. property: 'volume' | 'pitch' | 'gain'. driver: 'parameter:/Name' or 'event:/...'. driver_type: 'parameter' | 'timeline'. position: Parameter value or timeline seconds. value: Mapped property value.
Inputs: driver (required), target (required), property (required), value, +2 more.
automation_add_curveA
Bind a property to a curve so it changes as the driver changes —
e.g. crossfade music layers by automating each layer's volume
against an "Intensity" parameter. Reuses an existing curve for the
same target/property/driver if one exists (adding these points to
it) rather than creating a duplicate — call automation_list first
if unsure whether one's already there.
Args: target: Mixer group/bus/VCA/event mixer group {guid} — NOT a track guid (use mixerGroupGuid, not trackGuid). property: 'volume' | 'pitch' | 'gain'. driver: 'parameter:/Name' (parameter-driven) or 'event:/...' (timeline-driven). driver_type: 'parameter' | 'timeline'. points: [[position, value], ...]. Parameter-driven: position is a parameter value. Timeline-driven: position is seconds.
Inputs: driver (required), points (required), target (required), property (required), +1 more.
automation_listA
List the real automation curves + points on a target's automator for a given property — every curve's guid, the driver parameter it's bound to, and its actual [position, value] points.
Args: target: The automated object (mixer group, bus, VCA, event). property: 'volume' | 'pitch' | 'gain' (default 'volume').
Inputs: target (required), property.
bank_add_eventA
Assign an event to a bank (so it ships with the build).
Args: bank_target: bank:/ path or {guid}. event_target: event:/ path or {guid}.
Inputs: bank_target (required), event_target (required).
bank_createA
Create a bank to hold events and sounds.
Args: name: Bank name. Note: the "Master" bank always exists already.
Inputs: name (required).
bank_deleteB
Delete a bank and its contents.
Args: target: bank:/ path or {guid}.
Inputs: target (required).
bank_infoC
Get a bank's guid, name and path.
Args: target: bank:/ path or {guid}.
Inputs: target (required).
bank_listA
List every bank in the project (capped).
Inputs: no named parameters.
bank_list_eventsB
List the events assigned to a bank (capped).
Args: bank_target: bank:/ path or {guid}.
Inputs: bank_target (required).
bank_remove_eventA
Remove an event from a bank.
Args: bank_target: bank:/ path or {guid}. event_target: event:/ path or {guid}.
Inputs: bank_target (required), event_target (required).
bank_renameA
Rename a bank.
Args: target: bank:/ path or {guid}. name: New name.
Inputs: name (required), target (required).
event_add_marker_trackA
Get-or-create a marker (logic) track on an event's timeline.
Reuses an existing marker track if the event already has one (most
events only need one) — check event_list_tracks-style state before
assuming a fresh track is needed; call this and it will tell you
via reused.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_add_trackA
Add a group (audio) track to an event's timeline.
Returns two distinct GUIDs — a track and its mixer group are
different objects. Use trackGuid for sound_add_to_track
(placing instruments on the timeline). Use mixerGroupGuid for
automation_add_curve, mixer_group_volume, mixer_effect_add,
and anything else that operates on the mixer strip — a track
itself has no addAutomator().
Args: target: event:// path or {guid}. name: Optional mixer-group name for the track ("Audio 1" by default).
Inputs: target (required), name.
event_createB
Create an event in the master event folder (or an event:// folder).
Args: name: Event name (e.g. "Hit", "UI/Hover"). folder: Optional event:// path or {guid} of the owning folder.
Inputs: name (required), folder.
event_deleteC
Delete an event.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_infoB
Get an event's guid, name, path and maxVoices.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_key_offA
Send the keyoff command to a playing event instance — triggers the release behavior for any sustain point ahead of the playhead.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_listA
List every event in the project (capped).
Inputs: no named parameters.
event_list_tracksA
List an event's group tracks (mixer-group name + both guids each).
Args: target: event:// path or {guid}. include_master: Whether to include the event's master track (True).
Inputs: target (required), include_master.
event_lookupA
Resolve an event reference to its canonical event:/ path and guid.
Args: target: A path (event:/...) or {guid}.
Inputs: target (required).
event_playA
Play an event instance — the equivalent of pressing play in FMOD Studio's transport controls. This is how you actually hear a result instead of guessing from the event tree.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_playback_statusA
Check whether an event instance is playing/paused/stopping, and its current timeline playhead position — use this to validate a play/stop/pause call actually took effect.
Args: target: event:// path or {guid}.
Inputs: target (required).
event_return_to_startA
Return a playing/paused/stopping event instance's timeline playback position to the cursor (or to the timeline start, if the instance is stopped).
Args: target: event:// path or {guid}.
Inputs: target (required).
event_set_folderB
Move an event into a folder (or the master folder root).
Args: target: event:// path or {guid}. folder: event:// folder path or {guid}.
Inputs: folder (required), target (required).
event_set_max_voicesA
Cap simultaneous instances of an event (maxVoices).
Args: target: event:// path or {guid}. max_voices: 1-1000.
Inputs: target (required), max_voices (required).
event_set_nameC
Rename an event.
Args: target: event:// path or {guid}. name: New name.
Inputs: name (required), target (required).
event_stopA
Stop a playing event instance.
Args: target: event:// path or {guid}. immediate: True (default) stops instantly, skipping the stopping state. False lets release/fade-outs and one-shot tails play out before stopping.
Inputs: target (required), immediate.
event_timeline_cursorA
Scrub an event's timeline cursor to a position (in seconds).
Args: target: event:// path or {guid}. position: Cursor position in seconds (>= 0).
Inputs: target (required), position (required).
event_toggle_pauseC
Toggle the pause state of a playing event instance.
Args: target: event:// path or {guid}.
Inputs: target (required).
folder_createA
Find-or-create a folder chain (e.g. "UI/HUD" resolves/creates UI then HUD) — safe to call repeatedly, reuses existing folders.
Args: kind: EventFolder | AssetFolder. AssetFolder isn't creatable in FMOD Studio 2.03.14 (errors clearly rather than no-op'ing). path: Slash-separated, e.g. "UI/HUD".
Inputs: kind (required), path (required).
folder_listA
List folders in the project browser (capped).
Args: kind: Optional filter — EventFolder | AssetFolder. Omit for all.
Inputs: kind.
marker_add_namedA
Add a named (destination) marker — a labeled point on the timeline that transition markers/regions elsewhere can jump to. Errors if a marker with this name already exists on the track, rather than creating a duplicate — use marker_list to check first.
Args: track_target: Marker track {guid} from event_add_marker_track. name: Marker name. position: Timeline position in seconds (>= 0).
Inputs: name (required), position (required), track_target (required).
marker_add_regionB
Add a destination (loop) region to a marker track — a labeled range, e.g. a section transition markers/regions can jump into. Errors if a region with this name already exists on the track, rather than creating a duplicate.
Args: track_target: Marker track {guid} from event_add_marker_track. name: Region name. position: Start position in seconds (>= 0). length: Region length in seconds (> 0). loop_mode: None | Looping | Magnet (default Looping).
Inputs: name (required), length (required), position (required), track_target (required), +1 more.
marker_add_sustain_pointA
Add a sustain point — playback holds here until a keyoff command (event_key_off) releases it. Used for loop-until-released sounds (e.g. a footstep that holds mid-loop until the game says "stop").
Args: track_target: Marker track {guid} from event_add_marker_track. position: Timeline position in seconds (>= 0).
Inputs: position (required), track_target (required).
marker_add_transitionA
Add a transition marker — when playback crosses this point, the timeline jumps to the given destination.
Args: track_target: Marker track {guid} from event_add_marker_track. position: Timeline position in seconds (>= 0). destination_target: {guid} of a NamedMarker or LoopRegion (from marker_add_named / marker_add_region).
Inputs: position (required), track_target (required), destination_target (required).
marker_add_transition_regionA
Add a transition region — while playback is inside this range, the timeline jumps to the given destination.
Args: track_target: Marker track {guid} from event_add_marker_track. position: Start position in seconds (>= 0). length: Region length in seconds (> 0). destination_target: {guid} of a NamedMarker or LoopRegion.
Inputs: length (required), position (required), track_target (required), destination_target (required).
marker_add_transition_timelineA
Add a transition timeline to a transition marker/region/loop region/magnet region, with a source+destination sound pair — FMOD's "Add Transition Timeline" feature: a crossfaded transition instead of a hard jump-cut, the professional technique for a seamless loop.
Structurally verified live: this produces a valid TransitionTimeline
plus TransitionSourceSound/TransitionDestinationSound, both correctly
bound (a TransitionSourceSound/TransitionDestinationSound requires
both its audioTrack and parameter relationships set to be valid
— confirmed by creating one without them and observing isValid: false) and overlapped by crossfade_length seconds, which is what
makes FMOD blend them as a crossfade rather than play them back to
back. The exact blend hasn't been audibly verified against a real
render — audition it in Studio and adjust crossfade_length if the
blend isn't right; there's no scripted way to "listen" from here.
Args: transition_target: TransitionMarker/TransitionRegion/LoopRegion/ MagnetRegion {guid} to add the timeline to. audio_track_target: The GroupTrack {guid} whose audio is transitioning — the track being looped, for a simple single-track loop. crossfade_length: Overlap between outgoing and incoming audio, in seconds (default 1.0, must be > 0). Larger = smoother/slower blend.
Inputs: transition_target (required), audio_track_target (required), crossfade_length.
marker_deleteB
Delete a marker/region/sustain point/transition.
Args: target: Marker {guid}.
Inputs: target (required).
marker_listA
List every marker/region/sustain point/transition on a marker track (capped at 200), tagged with its marker type.
Args: track_target: Marker track {guid} from event_add_marker_track.
Inputs: track_target (required).
marker_renameA
Rename a named marker or region.
Args: target: Marker/region {guid}. name: New name.
Inputs: name (required), target (required).
marker_set_positionA
Move a point-type marker (named marker, sustain point, transition marker) to a new timeline position.
Args: target: Marker {guid}. position: New position in seconds (>= 0).
Inputs: target (required), position (required).
marker_set_regionA
Move/resize a region-type marker (loop region, transition region).
Args: target: Region {guid}. position: New start position in seconds (>= 0). length: New length in seconds (> 0).
Inputs: length (required), target (required), position (required).
mixer_effect_addB
Add an effect to a group's effect chain.
Args: target: Group path or {guid}. effect: Effect type, e.g. CompressorEffect, LimiterEffect, ParamEqEffect, LowpassEffect, DelayEffect, ConvolutionReverbEffect, DistortionEffect, ...
Inputs: effect (required), target (required).
mixer_effect_listB
List the effects on a group's chain.
Args: target: Group path or {guid}.
Inputs: target (required).
mixer_group_createB
Create a mixer group (routed to Master by default).
Args: name: Group name. output_target: Optional output bus/group path or {guid}.
Inputs: name (required), output_target.
mixer_group_deleteA
Delete a mixer group.
Warning: objects routed through it will need re-routing afterwards.
Args: target: Group path or {guid}.
Inputs: target (required).
mixer_group_infoA
Get a mixer group's guid, name, path and current volume (dB).
Args: target: Group path or {guid}.
Inputs: target (required).
mixer_group_listB
List every mixer group in the project (capped).
Inputs: no named parameters.
mixer_group_renameB
Rename a mixer group.
Args: target: Group path or {guid}. name: New name.
Inputs: name (required), target (required).
mixer_group_routeA
Route a group's output to a bus or group. Keep routing inside the same event/mixer surface — routing an event's master track into a different event's mixer has been known to crash Studio.
Args: target: Group path or {guid}. output_target: Destination bus/group path or {guid}.
Inputs: target (required), output_target (required).
mixer_group_volumeA
Set a mixer group's volume, in dB (-80 .. +10).
Args: target: Group path or {guid}. db: Volume in decibels.
Inputs: db (required), target (required).
mixer_master_infoA
Get the master bus guid, name and volume.
Inputs: no named parameters.
mixer_master_volumeA
Set the master bus volume, in dB (-80 .. +10).
Args: db: Volume in decibels.
Inputs: db (required).
mixer_send_createA
Create a return track + send within one event's mixer (e.g. a shared reverb bus). Per-event only — no cross-event/global send here.
Args: event_target: event:// path or {guid}, owns both the source group and the new return. source_group_target: Source mixerGroupGuid to send from. return_name: Name for the new return track. level_db: Send level in dB (-80..+10, default 0).
Inputs: return_name (required), event_target (required), source_group_target (required), level_db.
parameter_addA
Add a game parameter to an event. Errors if a parameter with this name already exists on the event, rather than creating a duplicate — use parameter_set_initial/parameter_list on the existing one instead.
The parameter is then settable by the game at runtime, or provides an automation line target on the event's timeline.
Args: event_target: event:/ path or {guid}. name: Parameter name. param_type: User | UserEnumeration | Distance | Direction | Elevation | EventConeAngle | EventOrientation. min: Minimum value (default 0). max: Maximum value (default 1).
Inputs: name (required), event_target (required), max, min, +1 more.
parameter_listA
List an event's game parameters (name + guid). A parameter's name
lives behind its presetOwner relationship, not a direct property —
don't read .name on the result of getParameterPresets() directly.
Args: event_target: event:/ path or {guid}.
Inputs: event_target (required).
parameter_set_initialA
Set a game parameter's initial value on an event.
Args: event_target: event:/ path or {guid}. parameter_name: Name of the parameter (from parameter_list). value: Initial value.
Inputs: value (required), event_target (required), parameter_name (required).
parameter_set_labelsA
Set enumeration labels on a UserEnumeration parameter.
Args: event_target: event:/ path or {guid}. parameter_name: The parameter's name. labels: Human-readable labels, in order (e.g. ["Off","Quiet","Loud"]).
Inputs: labels (required), event_target (required), parameter_name (required).
project_buildB
Build banks for the selected platform(s), or scope to specific banks/platforms (scoping a big project to one bank is much faster).
Args: banks: Bank name or list (default: every bank). platforms: Platform name or list (default: every platform).
Inputs: banks, platforms.
project_get_infoA
Get the open project's file path and display name.
Inputs: no named parameters.
project_get_modifiedA
Check whether the project has unsaved changes.
Inputs: no named parameters.
project_saveB
Save the open FMOD Studio project (the active .fspro).
Inputs: no named parameters.
project_save_allA
Save the project and every edited file (assets, banks, plugins).
Inputs: no named parameters.
snapshot_bind_groupA
Bind a mixer group's captured settings to a snapshot.
Snapshots store per-group mixer states. Binding a group to a snapshot tells Studio that group owns a setting within it, so later mixer edits while the snapshot is armed capture into that snapshot.
Args: snapshot_target: snapshot:/ path or {guid}. group_target: bus:/ or mixer group path/{guid}.
Inputs: group_target (required), snapshot_target (required).
snapshot_createB
Create a mixer snapshot.
A snapshot captures a set of mixer state changes (group/bus/VCA volumes, effect settings) that the game activates as a blendable state — e.g. a 'dungeon' or 'night' reverb/level shift layered over the base mix. Mixer settings are captured by Studio when you move a control while the snapshot is armed; pass the returned path to snapshot_bind_group to pin a group's current settings.
Args: name: Snapshot name.
Inputs: name (required).
snapshot_deleteA
Delete a mixer snapshot.
Args: target: snapshot:/ path or {guid}.
Inputs: target (required).
snapshot_infoA
Get a snapshot's guid, name and path.
Args: target: snapshot:/ path or {guid}.
Inputs: target (required).
snapshot_listA
List every mixer snapshot in the project (capped).
Inputs: no named parameters.
snapshot_renameB
Rename a mixer snapshot.
Args: target: snapshot:/ path or {guid}. name: New name.
Inputs: name (required), target (required).
sound_add_to_trackA
Place an instrument on an event's track timeline. Returned {guid} is for follow-up calls (sound_set_audio_file, sound_set_owner).
Args: event_target: event:/ path or {guid}. track_target: trackGuid (not mixerGroupGuid) from event_list_tracks. sound_type: SingleSound | MultiSound | ProgrammerSound | SoundScatterer | EventSound. start: Start position, seconds. length: Length in seconds (0 = untrimmed). name: Optional instrument name.
Inputs: sound_type (required), event_target (required), track_target (required), name, +2 more.
sound_createB
Create a standalone instrument (usually a SingleSound for a Multi's playlist).
Args: sound_type: SingleSound | MultiSound | ProgrammerSound | SoundScatterer | EventSound. name: Optional instrument name.
Inputs: sound_type (required), name.
sound_infoA
Get an instrument's guid, name, path, and whether it actually has an audio asset attached (hasAudioFile / audioFileName) — a SingleSound with no audio assigned shows an empty box with no waveform in Studio and plays silence; check this after sound_set_audio_file rather than assuming the assignment stuck.
Args: target: Instrument {guid} or path.
Inputs: target (required).
sound_set_audio_fileA
Assign an imported audio asset to an instrument.
Reads the assignment back before returning — a guid alone isn't
proof the audio actually attached, only that the JS call didn't
throw. If audioFileGuid comes back null, the assignment silently
didn't take (this raises instead of reporting a false success).
Args: target: Instrument {guid} or path. audio: Asset {guid} from audio_import.
Inputs: audio (required), target (required).
sound_set_nameA
Rename an instrument.
Args: target: Instrument {guid} or path. name: New name.
Inputs: name (required), target (required).
sound_set_ownerB
Set a sound's owning instrument (e.g. a SingleSound into a MultiSound).
Reads the assignment back before returning — see sound_set_audio_file.
Args: target: SingleSound {guid}. owner: Owner MultiSound/Scatterer {guid}.
Inputs: owner (required), target (required).
utility_deleteA
Delete any object from the project.
Warning: destructive and not undoable from the terminal.
Args: target: Object path or {guid}.
Inputs: target (required).
utility_dumpA
Real introspection: every plain property (with value) + every
relationship (cardinality + count) on a live object. Use this BEFORE
concluding a capability "doesn't exist" — FMOD's docs only list
methods, not plain properties (e.g. looping), and FMOD's own
dump() only logs to Studio's console and returns nothing here.
Args: target: Object path or {guid}.
Inputs: target (required).
utility_is_validC
Check whether an object is valid (survived recent edits).
Args: target: Object path or {guid}.
Inputs: target (required).
utility_listB
List every object of a given type (capped).
Args: obj_type: Event | Bank | MixerGroup | MixerBus | MixerVCA | Snapshot | Folder | Preset.
Inputs: obj_type (required).
utility_lookupB
Resolve any object (event, bank, group, asset, ...) to its identity.
Args: target: Path (event:/..., bank:/...) or {guid}.
Inputs: target (required).
utility_validateB
Run the project's validation and report issues.
Inputs: no named parameters.
vca_assignA
Assign a mixer strip (group/bus) to a VCA so the VCA's fader scales it alongside every other strip assigned to it.
FMOD's docs don't name the exact assignment relationship — this tries a couple of plausible names and raises a clear error instead of silently doing nothing if neither applies.
Args: vca_target: vca:/ path or {guid}. strip_target: Mixer group/bus path or {guid} to assign.
Inputs: vca_target (required), strip_target (required).
vca_createA
Create a VCA (Voltage-Controlled Amplifier) — a volume control that scales every mixer strip assigned to it, for grouping several buses under one fader (e.g. "Music", "SFX", "Voice").
Args: name: VCA name.
Inputs: name (required).
vca_infoA
Get a VCA's guid, name and current volume (dB).
Args: target: vca:/ path or {guid}.
Inputs: target (required).
vca_listA
List every VCA in the project (capped).
Inputs: no named parameters.
vca_volumeA
Set a VCA's volume, in dB (-80 .. +10).
Args: target: vca:/ path or {guid}. db: Volume in decibels.
Inputs: db (required), target (required).
workspace_browser_currentA
Get the object currently selected in the project browser.
Inputs: no named parameters.
workspace_editor_selectionB
Get the object currently selected in the open editor window.
Inputs: no named parameters.
workspace_infoA
Get the workspace's key roots: event/asset/bank roots and the master bus.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 92 tools
Many tools are clearly scoped by resource type, but there are several overlapping boundaries: generic utility_delete/utility_lookup/utility_list duplicate specific delete/lookup/list tools, project_save and project_save_all are near-twins, and automation_add_curve vs. automation_add plus the marker_add_transition* family are easy to confuse. The detailed descriptions help, but an agent navigating 92 tools will still face selection ambiguity.
The set overwhelmingly follows a consistent lowercase snake_case [domain]_[operation] pattern, e.g. event_create, bank_delete, mixer_group_volume, sound_set_owner. Minor exceptions like workspace_editor_selection, workspace_browser_current, and audio_assets break the verb pattern slightly, but overall naming is predictable and readable.
92 tools is far beyond what an MCP server should expose, even for a complex domain like FMOD Studio. The rubric treats 50+ as an extreme mismatch; this server has nearly double that, which is excessive for agent context windows and creates unnecessary selection burden. Many tools could be consolidated into parameterized operations.
The domain is broadly covered: events, banks, mixer groups, VCAs, snapshots, markers, parameters, automation, audio assets, project save/build, and workspace navigation are all represented. There are minor gaps such as no dedicated VCA delete/rename, no parameter delete/rename, no effect removal, and no sound deletion, but utility_delete and related generic tools provide workarounds.
Maintenance
Related MCP Connectors
Make games with AI: one MCP server that connects your agent to Unity, Unreal and Godot editors.
Generate game-ready 3D models, textures, and audio from natural language, over MCP.
MCP server for Producer/Riffusion AI music generation
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to FL Studio for music production via Virtual MIDI. It enables users to control transport, manage the mixer, write notes, and manipulate plugin parameters through natural language.1MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables AI coding agents to control FMOD Studio for audio import, event creation, and bank building via TCP scripting.211MIT
- AlicenseAqualityBmaintenanceA modular suite of MCP servers for Audiokinetic Wwise, enabling AI agents to browse, edit, audition, profile, and build Wwise projects through the Wwise Authoring API.155Apache 2.0
- AlicenseCqualityCmaintenanceAn MCP server that drives FMOD Studio live through its scripting terminal, exposing the FMOD Studio Scripting API as MCP tools for immediate project editing.10038 PyPI16MIT