https://blog.ast.moe/en/tags/cubase/Recent posts: GorimuchuHugohttps://blog.ast.moe/en/blog/2026-09-19-2/Sat, 19 Sep 2026 20:28:17 +0900https://blog.ast.moe/en/blog/2026-09-19-2/<p>Previously, I wrote an article titled “Building a Server to Control Cubase via MCP” (<a href="https://blog.ast.moe/en/blog/2026-08-16/">source</a>).</p> <p>Since then, I’ve continued developing <span> <a target="_blank" href="https://github.com/ieee0824/cubase_mcp"> cubase_mcp </a> <img class="external-link-icon" src="https://blog.ast.moe/images/outer-link.png" width="12" height="12" alt="" aria-hidden="true" loading="lazy"> </span> , but it hasn’t progressed as much as I had hoped.</p> <p>I’ve now managed to handle play/stop and retrieve transport status, so the next step is to obtain a list of the project’s tracks.</p> <p>If we can retrieve information such as the track name, selection state, mute, and solo status, we could expand what’s possible from MCP. That was the premise, but now I’m still investigating what exactly can be retrieved and how far.</p>https://blog.ast.moe/en/blog/2026-08-16/Sun, 16 Aug 2026 08:05:11 +0900https://blog.ast.moe/en/blog/2026-08-16/<p>I thought it would be interesting to control Cubase via MCP, so I created the <a href="https://github.com/ieee0824/cubase_mcp">Cubase MCP</a>.</p> <p>By sending commands such as “play,” “stop,” or “report the current status” from an MCP client, you can operate Cubase’s transport controls and retrieve its state.</p> <p>It’s not yet possible to control every aspect of Cubase. This time, I first built a small implementation that simply connects MCP to Cubase.</p> <h2 id="what-was-created">What was created</h2> <p>The implementation is an integration daemon written in Rust.</p>