fmod-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FMOD_MCP_HOST | No | Host for the FMOD Studio TCP scripting terminal | 127.0.0.1 |
| FMOD_MCP_PORT | No | Port for the FMOD Studio TCP scripting terminal | 3663 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingB | Sanity-check the FMOD Studio connection. Returns version if available. |
| list_banksA | List every bank in the currently open project. |
| list_eventsA | List events, optionally filtered by path prefix (e.g. 'event:/bumpers/'). |
| list_busesA | List every mixer bus in the currently open project. |
| get_eventC | Return tracks, instruments, and bank assignments for one event. |
| import_audioB | Import a local .wav/.ogg into the project's audio bin. |
| create_eventC | Create an empty event, assign it to a bank, optionally route to a bus. Missing parent folders in event_path are created automatically. |
| add_single_soundC | Add a new group track with a Single-Sound instrument to an event. |
| set_event_propertyC | Set a scalar property on an event (volume, pitch, etc.). |
| assign_to_bankC | Add the event to the given bank (event can live in multiple banks). |
| assign_to_busC | Route the event's master track output to a mixer bus. |
| list_effect_typesA | List every effect class name available in the current Studio. |
| add_effectA | Add a new effect to a bus or event-track effect chain. target_path is |
| list_effectsB | List effects on a bus or event-track chain (excludes the built-in fader). |
| get_effectB | Return parameters, bypass, and chain location for an effect. |
| set_effect_paramB | Set an effect parameter (e.g. decayTime, gain, threshold). |
| remove_effectC | Remove an effect from its chain. |
| bypass_effectC | Toggle bypass on an effect. |
| save_projectA | Save the open FMOD Studio project. Must be called before build_banks. |
| build_banksB | Build banks for the default platform. Can take a minute or two. |
| run_jsA | Evaluate arbitrary JavaScript in the Studio scripting terminal. Your snippet is wrapped in an IIFE, so use |
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 21 tools
Most tools target distinct resources and actions. However, create_event already includes assignment to bank and bus, creating some overlap with assign_to_bank and assign_to_bus.
All tools follow a consistent verb_noun pattern (e.g., add_effect, list_events, set_event_property). Prepositions in assign_to_bank are acceptable and consistent.
21 tools is slightly high but still well-scoped for the FMOD Studio domain. Each tool serves a distinct purpose without excessive redundancy.
Core workflows like event creation, effect management, and building are covered. Notable gaps include no delete operations for events or sounds, and no update beyond property setting.