A
licenseB
qualityC
maintenanceAn MCP server that enables AI coding agents to control FMOD Studio for audio import, event creation, and bank building via TCP scripting.
21
1
MIT
FmodStudioMCP
by xDarkzx
Related Servers
Alternatives to FmodStudioMCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceAn MCP server that drives FMOD Studio live through its scripting terminal, exposing the FMOD Studio Scripting API as MCP tools for immediate project editing.10011MIT
- AlicenseAqualityCmaintenanceA 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
- 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
- FlicenseAqualityAmaintenanceMCP server that connects AI coding assistants to a live Godot editor, enabling scene, node, script, resource, runtime, debugger, and test workflows through natural language.45-
- AlicenseNot gradedqualityDmaintenanceA comprehensive audio MCP server that enables AI agents to generate speech, transcribe audio, clone voices, analyze speech quality, design soundscapes, and manage audio assets through a standardized interface.2MIT
TDQS
B3.2/5.0
Scored across 92 tools
Disambiguation3/5
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.
Naming Consistency4/5
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.
Tool Count1/5
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.
Completeness4/5
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
ActivityMaintained
ResponsivenessNo issues