MCP server that drives FMOD Studio live via its scripting terminal (TCP 3663) — one tool per Scripting API member, ge...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Claude
Fastest way to find out if fmod-studio-mcp belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add fmod-studio-mcp -- npx fmod-studio-mcpRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove fmod-studio-mcpNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ fmod-studio-mcp ← registers here
MCP server that drives FMOD Studio live via its scripting terminal (TCP 3663) — one tool per Scripting API member, generated from the API reference.
Source: GitHub repository
Source check: October 12, 2026
Upstream commit: October 12, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.