Install Studio
Download mcut Studio for macOS or Linux, launch it the first time, and find the bridge token it writes.
mcut Studio is a desktop app. It bundles the editor and the live MCP bridge in
one process, so an agent connects to the running app without a separate server.
Builds for macOS and Linux are published on GitHub Releases. The
desktop releases
carry the installers mcut-studio-<version>-mac-arm64.dmg,
mcut-studio-<version>-mac-x64.dmg, and
mcut-studio-<version>-linux-x86_64.AppImage, plus the files the in-app
updater reads. Releases are tagged mcut-desktop@<version> and marked
prerelease while the version is 0.x. Windows is not supported in the first
release.
macOS
-
Download
mcut-studio-<version>-mac-<arch>.dmgfor your chip. Apple silicon Macs takearm64, Intel Macs takex64. -
Open the disk image and drag mcut Studio into Applications.
-
Open it. Releases are signed with a Developer ID certificate and notarized by Apple, so the first launch opens with a double-click.
Versions built before signing was configured are signed ad hoc and are not notarized. For those, the first launch stops on a Gatekeeper dialog. Click Done, open System Settings, Privacy & Security, and click Open Anyway next to mcut Studio, as described in Open a Mac app from an unknown developer.
Linux
- Download
mcut-studio-<version>-linux-x86_64.AppImage. - Make it executable and run it.
chmod +x mcut-studio-<version>-linux-x86_64.AppImage
./mcut-studio-<version>-linux-x86_64.AppImageAn AppImage mounts itself with FUSE. On a machine without FUSE, run it with
--appimage-extract-and-run, as described in the
AppImage FUSE troubleshooting guide.
First launch
The window opens on the editor. The app starts the live MCP bridge on port
44737 and prints two lines on standard output when it is up.
BRIDGE_READY ws://127.0.0.1:44737/mcut-mcp
MCP_URL http://127.0.0.1:44737/mcp?token=<token>The MCP menu in the app has Copy MCP URL and Add to Cursor. See Connect Cursor for the client side.
The bridge token
The app generates a token on first launch and keeps it in its user data directory, so the MCP URL stays the same across restarts.
| Platform | Token file |
|---|---|
| macOS | ~/Library/Application Support/mcut-desktop/bridge-token |
| Linux | ~/.config/mcut-desktop/bridge-token |
The file holds one line of 64 hex characters. Delete it to rotate the token. The next launch writes a new one, and every client that stored the old URL has to be reconnected.
Updates
Studio checks GitHub Releases for a newer desktop build when it launches and every four hours after that. When one exists, a dialog shows the version and its release notes. The download starts when you ask for it, and the app restarts to install when you choose Restart to update. A downloaded update you leave for later installs when the app quits.
On macOS an update installs only from a Developer ID signed and notarized build. An ad-hoc signed build logs that auto-update is off and never shows the dialog. On Linux the update replaces the AppImage in place, so keep it in a directory you can write to.
Releases under 1.0.0 are prereleases, and a 0.x install follows
prereleases. A 1.x install only follows releases that are not marked
prerelease.
Local projects
Studio saves projects as .mcut.json files through the native save dialog.
Any project file the CLI or the
stdio MCP server produces opens in Studio through
File, Open project.