Game music loops for AI agents: seamless loops with the reverb tail, Sections, and engine kits.
Use Loopsmith from AI apps that support MCP (the Model Context Protocol), such as Claude, Codex and Cursor.
Loopsmith prepares finished game music for game engines: seamless loops that keep the reverb tail, music in sections the game moves between, and FMOD Studio, Wwise and Unreal kits, plus ready-made players for Unity, Godot and the web. With this, an AI agent working on your game can pick up the loop points you set by ear in Loopsmith, export them into your project, and write the code that plays them.
This package is a small launcher. It finds the Loopsmith app on your computer and starts the MCP server that comes with it. Everything runs on your own computer: no account, nothing sent anywhere.
npx.Without Loopsmith installed, the server offers one tool that says where to get it.
Add this to your AI app's MCP servers:
{
"mcpServers": {
"loopsmith": {
"command": "npx",
"args": ["-y", "loopsmith-mcp"]
}
}
}
Claude Code:
claude mcp add loopsmith -- npx -y loopsmith-mcp
Or skip this package entirely: in Loopsmith, open Help > Use with an AI app... and it adds itself to Claude, Claude Code, Cursor or Codex for you.
Then quit the AI app and open it again, and ask it to "read Loopsmith's guide".
loopsmith_guide, analyze_render, check_seam, read_saved_loop, read_project, export_loop
(with kit for FMOD, Wwise or Unreal), check_sections, render_join and export_sections. The
Loopsmith manual's "Use Loopsmith from an AI app" chapter describes each one.
LOOPSMITH_MCP_EXE, if you set it to the full path of loopsmith-mcp.exe.%LOCALAPPDATA%\Programs\Loopsmith and %LOCALAPPDATA%\Programs\Loopsmith Demo.MIT for this launcher. Loopsmith itself is a separate, paid app with a free demo.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y loopsmith-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-composingkeys-loopsmith": {
"command": "npx",
"args": [
"-y",
"loopsmith-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceloopsmith-mcpnpmio.github.composingkeys/loopsmith works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.