Skip to main content

Trackwright

English · Español

PyPI version CI Python 3.14+ License: AGPL v3+ Coverage 98% Platform: macOS DAW: Cubase 15.0.20+ MCP

Trackwright is an independent MCP server for controlling digital audio workstations (DAWs).

It lets an AI assistant (Claude, GitHub Copilot or any other MCP client) inspect and control your DAW: tracks, mixing, plugins and their parameters, transport, markers, automation and time-range editing designed for podcasts.

The first implementation supports Cubase. It works through a MIDI Remote script that runs inside Cubase and needs no hardware controllers or IAC ports. Other DAWs may follow: much of the core (MIDI transport, bridge, write policy, verification by reading back) does not depend on Cubase.

Package trackwright
Executable trackwright
MCP server trackwright (stdio)
MCP clients Any client that supports stdio servers. Tested with Claude Code
Platform macOS. Verified on macOS 27.2 (Apple Silicon)
DAW Cubase 15.0.20 or later (MIDI Remote API 1.3). Verified on Cubase Elements 15.0.30
License AGPL-3.0-or-later

Trackwright is an independent project. It is not affiliated with or endorsed by Steinberg; Cubase is a trademark of Steinberg Media Technologies GmbH.

Requirements

  • uv 0.13 or later (brew install uv). You don't need to install Python: uv downloads the right one. There is nothing to compile.
  • Cubase 15.0.20 or later.
  • An MCP client: Claude Code (tested), Claude Desktop, GitHub Copilot in VS Code or any other client that supports stdio servers.

Installation

uv tool install trackwright
trackwright setup

If the terminal can't find trackwright, run uv tool update-shell and open a new terminal.

trackwright setup is a guided installation. At each step it shows what it is going to do and asks before applying it (the default answer is "no"):

  1. copies the Trackwright_Bridge.js script into the Cubase MIDI Remote folder (~/Documents/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local/trackwright/bridge/);
  2. creates ~/.config/trackwright/config.toml if it doesn't exist, asking whether writes, project saving and reading audio files for analysis are allowed (default: no);
  3. registers the server in Claude Code (claude mcp add --scope user trackwright …) or, if it can't find claude, shows you the command;
  4. checks everything with trackwright doctor.

It never uses sudo and never changes Cubase or system settings. To skip the question for a step: --yes script, --yes config or --yes claude.

Activate the script in Cubase

  1. Restart Cubase (it doesn't reload scripts on its own) and open a project. For the first tests, a throwaway one is best.
  2. The Trackwright – Bridge surface should appear in the MIDI Remote tab of the lower zone. Trackwright creates the virtual ports when it starts, and your MCP client starts the MCP server. If the surface doesn't appear, click + Add MIDI Controller Surface and choose Trackwright / Bridge, with input Trackwright To Cubase and output Trackwright From Cubase.
  3. Recommended: in Studio > Studio Setup > MIDI Port Setup, uncheck "In 'All MIDI Inputs'" for Trackwright To Cubase.

Check

trackwright doctor   # checks every link and tells you what to do if something fails

Then, in your MCP client (for example, Claude Code): "Check the Cubase status with Trackwright".

Try it without Cubase

Trackwright includes a simulated Cubase. To try it from Claude Code without installing anything else:

claude mcp add trackwright-sim -- uvx trackwright serve --simulate

Other MCP clients

trackwright setup registers the server in Claude Code. Any other MCP client needs the same command: trackwright serve over stdio. Desktop apps don't inherit your terminal's PATH, so use the absolute path shown by which trackwright.

GitHub Copilot in VS Code (not tested yet): run MCP: Open User Configuration and add:

{
  "servers": {
    "trackwright": {
      "type": "stdio",
      "command": "/Users/<you>/.local/bin/trackwright",
      "args": ["serve"]
    }
  }
}

Then use Copilot Chat in agent mode. The Trackwright tools appear in its tool list.

Claude Code plugin: producer skills

The plugin adds skills that chain the tools into a producer's job, asking you before changing anything:

  • podcast-silence-trim: "remove the silences longer than 3 seconds". Measures an export, shows every proposed cut and closes the gaps on all tracks.
  • noise-gate: "put a noise gate on the Voice track". Finds the gate plugins you have (Cubase's or third-party), measures the noise and the quietest speech, and proposes the threshold.
/plugin marketplace add impalah/trackwright
/plugin install trackwright@trackwright

The plugin starts its own server, so install the Cubase script with trackwright setup but answer no when it offers to register the server in Claude Code (or remove an earlier registration with claude mcp remove trackwright --scope user). The skills need [writes] enabled = true and [analysis] enabled = true. Details in the plugin manual.

Update and uninstall

  • Update: uv tool upgrade trackwright, trackwright bridge-stop (the MCP server starts the new bridge when it needs it) and trackwright setup, which updates the Cubase script if it changed. Restart Cubase and your MCP client. The changelog lists the steps of each version.
  • Uninstall:
    1. claude mcp remove trackwright -s user;
    2. trackwright bridge-stop;
    3. uv tool uninstall trackwright;
    4. delete ~/Documents/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local/trackwright/ and ~/.config/trackwright/, and remove the surface in the Cubase MIDI Remote tab.

What it can do (Cubase)

33 tools, all with structured output:

  • Reading: status, mixer tracks, selected channel, inserts, plugin catalog, parameters, transport and recent changes.
  • Writing, always with a dry run (dry_run) and verification by reading back: parameters (as normalized values or in real units), plugin insertion, volume, mute, solo, record arm, track name and tempo.
  • Navigation: select tracks and move the cursor and the locators.
  • Automation: records volume, pan, send, channel EQ, pre-filter and plugin parameter curves by playing the project, with values in real units (dB, Hz) converted by Cubase. Verified on Cubase Elements.
  • Podcast editing: delete, cut or insert silence over a range in seconds, on all tracks or on one, with verification of the result.
  • Project settings: read time signature, cycle, metronome, count-in, punch…; change cycle, metronome, count-in, punch, pre-roll and post-roll, and click level.
  • Plugin presets: next or previous, verified by the change in parameters. The preset name is not available through the API.
  • Save the project: only on request, with its own permission ([writes] save), dry run and verification by the file's timestamp.
  • Import audio: on the given track and position, with the Cubase file picker, and verification by the edges of the new event.
  • Export the mix: of a range or of the whole project, with the Cubase dialog, and confirmation of the created file.
  • Analyze audio: noise floor, levels and silences of an exported file, in project seconds. Reading audio has its own permission ([analysis] enabled).
  • Producer skills for Claude Code: trim the silences of a podcast and set a noise gate, through the plugin (see above).
  • Cubase commands: markers, track deletion, splitting at the locators, track creation with the user's help, and a list of allowed commands. Each command states how it behaves: whether it acts directly, opens a dialog or asks for confirmation.

By default it only reads. Writes are enabled in the configuration and can be limited to specific tracks.

Security

  • Read-only by default. Writes are enabled in ~/.config/trackwright/config.toml ([writes] enabled = true) and can be limited to specific tracks (allowed_tracks). Saving the project has its own permission ([writes] save).
  • Every write supports a dry run (dry_run) and is verified by reading back the state. A write whose result is uncertain is not retried.
  • It opens no network ports: the server talks to the MCP client over stdio and to the bridge over a private Unix socket.
  • It doesn't close Cubase, doesn't record audio and doesn't save anything unless asked.

Configuration

# ~/.config/trackwright/config.toml
[writes]
enabled = true                   # allow changes to the open project
save = false                     # allow saving the project on request
# allowed_tracks = ["Voice"]     # limit writes to these tracks

[cubase]
app = "Cubase 15"                # application name for cubase_launch

trackwright config shows the effective configuration.

Known limitations

  • Not possible through the API: changing routing (inputs, outputs or sends), reading track contents (events, audio or automation) or completing Cubase dialogs.
  • Only tracks with a mixer channel are visible.
  • Importing audio, exporting the mix and changing presets use Cubase dialogs or windows: Trackwright opens and prepares them, and you complete the dialog.
  • For now, macOS only and Cubase only.

Status

Alpha version. Every tool has been run against Cubase Elements 15.0.30 on macOS 27.2, with visual confirmation where the API cannot observe the result. It also has unit tests, MCP contract tests, script tests with Node.js and end-to-end tests, with 98 % coverage.

Documentation

Manuals and tutorials are in the docs/ folder of the repository, in English with Spanish translations (Spanish index). Source code and issues: github.com/impalah/trackwright.

License

Copyright (C) 2026 impalah.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 or, at your option, any later version (AGPL-3.0-or-later). It is distributed without any warranty. See the LICENSE file.

Metadata

Release files for trackwright 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for trackwright 0.5.0
File Size Uploaded Provenance Actions
trackwright-0.5.0.tar.gz 148.1 kB Without provenance Details for trackwright-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for trackwright 0.5.0
File Interpreter ABI Platform Actions
trackwright-0.5.0-py3-none-any.whl Python 3 none any Details for trackwright-0.5.0-py3-none-any.whl

Total release size: 314.7 kB

Release files / trackwright-0.5.0.tar.gz

Download URL trackwright-0.5.0.tar.gz
Size 148.1 kB
Tags Source
SHA-256 checksum
How to use checksums
84695342c353e8608cacbadd4dddddd9b6e29ab73c4734cd044109b09e99614b
BLAKE2b-256 checksum
How to use checksums
46cfdca7753db3b4cd10c5dca30dc0223ca7d52b8cee431b5742155781765511
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / trackwright-0.5.0-py3-none-any.whl

Download URL trackwright-0.5.0-py3-none-any.whl
Size 166.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
966b4206f6421aa227c0f88d63aaa3be58caa096da1b9c5f53128ee582cc346a
BLAKE2b-256 checksum
How to use checksums
9d4d86eb5c5494e63bbdc3f5413ae1e7b55f71e25d345d4c7316d51089840c10
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for trackwright 0.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page