An MCP server that drives FMOD Studio live
through its built-in (TCP, default ). Unlike
file-based approaches that edit a project's XML on disk (and require closing/reopening
Studio), this talks to the editor: changes appear immediately, and Studio
itself writes them — so there's no clobbering and no reload dance.
MCP server that drives FMOD Studio live via its scripting terminal (TCP 3663) — one tool per Scripting API member, generated from the API reference.
ดาว
15
เครื่องมือ
—
อัปไทม์
—
scripting terminal
127.0.0.1:3663
running
It exposes the FMOD Studio Scripting API
as one MCP tool per API member — generated from the crawled reference, not
hand-written — plus a few generic tools for the parts the static docs can't enumerate.
There is no arbitrary-script / eval tool: every capability is a named,
schema-validated operation over FMOD's object model.
⚠️ Alpha. Built for an AI agent (Claude Code) to author game audio. It edits the
live project — call fmod_project_save to persist, and keep it version-controlled.
How it works
FMOD Studio's Script Server exposes the scripting terminal over a TCP port: it
evaluates anything it receives as UTF-8 JavaScript and returns the result as text.
It's disabled by default — enable it once in Studio's preferences (see
FMOD Studio setup). Opening the console
with Ctrl + 0 shows script output but does not start the server. This MCP keeps
one connection and uses read-until-idle framing, so it doesn't depend on a particular
prompt string.
Each tool generates the small piece of scripting-API JavaScript for its member, runs it,
and returns the result as a string. Anything that returns an object reports that object's
path or {guid}, so results chain straight back in as another tool's target.
The tool set
Generated — one per documented member (~148). Named fmod_<Owner>_<member>, e.g.
fmod_project_create, fmod_project_importAudioFile, fmod_Event_addGroupTrack,
fmod_GroupTrack_addSound, fmod_Bank_getPath, fmod_system_getText. A member's
target_kind decides how it's reached:
Method args are auto-embedded: numbers/booleans as JS literals, a path
(event:/…, bank:/Master) or {guid} as an object reference (lookup(...)), else a
string. Settable properties take an optional value (omit to read).
Generic — reach the dynamic, schema-defined members the static docs don't list
(an event's timeline, an instrument's audioFile, a sound's pitch/looping, …):
Tool
Purpose
fmod_get_property
Read any property of an object, including per-class managed properties.
fmod_set_property
Set any property (e.g. instrument audioFile = an asset).
fmod_add_relationship / fmod_remove_relationship
Edit a relationship (e.g. event banks → a bank).
fmod_class_names
List the project model's class names.
fmod_describe_class
List a class's schema-defined property + relationship names (discovery).
FMOD Studio 2.02+, with a project open and the Script Server enabled
(Preferences → Interface → Script Server, port 3663 — requires a restart; see
FMOD Studio setup below). Opening the
console (Ctrl+0) alone does not start it.
Python 3.10+.
FMOD Studio setup — enable the Script Server
The scripting terminal's TCP server (Script Server) is off by default, and opening
the console with Ctrl + 0 is not enough — that only shows script output. Enable it once:
Launch FMOD Studio and open your project (File → Open Project… → your .fspro).
Open Preferences — FMOD Studio → Preferences… (⌘,) on macOS, Edit → Preferences…
on Windows.
Select the Interface tab — the Script Server section is at the top. Set:
✅ Enable Script Server (requires restart)
Port:3663 (must match FMOD_STUDIO_PORT, default 3663).
Quit and relaunch FMOD Studio, then reopen the project. The setting only takes effect
after a restart.
(optional) Open the console with Ctrl + 0 to watch script output as tools run.
Verify it's listening
# macOS / Linux
nc -z 127.0.0.1 3663 && echo "listening ✓"
lsof -nP -iTCP:3663 -sTCP:LISTEN # shows the fmodstudio process bound to 3663
On every launch, FMOD records the Script Server state in its log:
[Scripting] ScriptServer started on 127.0.0.1 (3663) ← enabled ✅
[Scripting] ScriptServer is disabled. ← not enabled ❌
Cannot reach FMOD Studio's scripting terminal… — the Script Server isn't running.
Grep the newest log for ScriptServer is disabled; if present, enable it in Preferences
and restart (the checkbox literally says "requires restart" — toggling without
relaunching won't bind the port).
Enabled but still nothing on 3663 — confirm a project is open (the server won't
bind on the start/welcome screen) and that no other app holds the port.
Port mismatch — the Preferences port and FMOD_STUDIO_PORT must be the same value.
Install
Run it straight from PyPI with uv — no clone, no venv.
uvx downloads and launches it on demand:
Keywords: FMOD Studio MCP server · FMOD scripting API automation · AI game-audio tooling · Model Context Protocol server for FMOD · Claude / LLM game-audio agent · programmatic FMOD Studio control · game sound-design automation.
F
Fmod Studio
EYamanS·15 ดาว·
MCP server that drives FMOD Studio live via its scripting terminal (TCP 3663) — one tool per Scripting API member, generated from the API reference.
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
Fmod Studio ต้องใช้ API key ไหม?
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Fmod Studio ใช้ทรานสปอร์ตแบบใด?
Fmod Studio ทำงานแบบโลคัลผ่าน stdio
Fmod Studio ถูกตรวจสอบล่าสุดเมื่อใด?
ตรวจสอบล่าสุดเมื่อ 2026-10-28 MCP server that drives FMOD Studio live via its scripting terminal (TCP 3663) — one tool per Scripting API member, generated from the API reference.