Connect Maxxlorr Tracker to MCP
Keep the downloaded launcher in the complete MLT application folder, next to index.html and the mcp folder. A launcher by itself is not the complete application. Browsers download these files; they do not run them automatically.
- Download and run MCP.cmd on Windows, or Setup MCP.command on macOS/Linux. Node.js 22 or newer is required. First setup installs pinned dependencies if needed; later launches work offline.
- Copy the configuration below into your MCP client's server settings. Add this entry without replacing existing servers. Restart or reconnect your client when it requests it.
- The client starts MLT and opens its browser automatically. Click MCP in MLT, choose permissions, then Connect. Editing, playback and audio export remain separate choices.
Moving the distribution folder? Run setup again and update your client's entry. Do not double-click server.mjs: the MCP client owns its connection. Each client may start a separate MLT tab. Closing the client stops its companion.
No automatic client configuration changes, public network listener or
permission grants. Browser and operating-system restrictions can block
automatic opening; the client can also call
mlt_instances to obtain the local launch address.
macOS may require permission to open the launcher. Linux users can run
sh "Setup MCP.command". For portable distribution, supply
an official Node runtime at runtime/node.exe (Windows) or
runtime/bin/node (macOS/Linux), retaining its license.