ableton-mcp

by cavi-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

export_audio_mix

Destructive

Export Ableton Live's Main mix to a new stereo WAV file by setting render start, length, sample rate, and bit depth.

Instructions

Export Main as stereo WAV through the macOS English Live dialog. Requires stopped transport, recording off, unarmed tracks and an absent destination. Rechecks document/mix controls and verifies native settings and file format. Full-range render completion remains unconfirmed. Current Session overrides are included. Updates export preferences; no overwrite or musical-quality claim.

Input Schema

Name	Required	Description
`path`	Yes	Absolute new .wav path; parent directory must exist.
`start`	Yes	Native render start as bars.beats.sixteenths, e.g. 1.1.1.
`dryRun`	No	False executes with token and hash.
`length`	Yes	Native render length, e.g. 4.0.0 for four bars; include intended tails.
`bitDepth`	No	Defaults to 24; 32 uses floating point.
`planHash`	No	Plan hash.
`sampleRate`	No	Defaults to 48000 Hz.
`confirmationToken`	No	Single-use plan token.
`expectedStateVersion`	Yes	Observed stateVersion.
`expectedSetFingerprint`	Yes	Current Set fingerprint from get_live_state.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 23, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "oneOf": [
+      {
+        "properties": {
+          "confirmation": {
+            "properties": {
+              "expiresAt": {
+                "type": "number"
+              },
+              "planHash": {
+                "pattern": "^[a-f0-9]{64}$",
+                "type": "string"
+              },
+              "token": {
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "required": [
+              "token",
+              "planHash",
+              "expiresAt"
+            ],
+            "type": "object"
+          },
+          "dryRun": {
+            "const": true
+          },
+          "plan": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "plan",
+          "confirmation"
+        ],
+        "type": "object"
+      },
+      {
+        "properties": {
+          "dryRun": {
+            "const": false
+          },
+          "operationOutcome": {
+            "properties": {
+              "evidence": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "reason": {
+                "type": "string"
+              },
+              "schemaVersion": {
+                "const": 1
+              },
+              "status": {
+                "enum": [
+                  "applied",
+                  "outcome_unknown",
+                  "postconditions_failed",
+                  "pending_postconditions",
+                  "pending_user_action"
+                ]
+              }
+            },
+            "required": [
+              "schemaVersion",
+              "status",
+              "reason",
+              "evidence"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "operationOutcome"
+        ],
+        "type": "object"
+      }
+    ],
+    "properties": {
+      "dryRun": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "dryRun"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Addedv0.3.0Oct 19, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the macOS English Live dialog dependency, the re-verification of document/mix controls and native settings, that Session overrides are baked into the render, that export preferences are mutated, and that full-range render completion is not confirmed. The 'no overwrite or musical-quality claim' line explicitly disclaims guarantees the agent might otherwise assume, which is exactly the kind of residual-risk context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause and every following sentence carries semantic load (preconditions, verification, limitations). The telegraphic closing fragment 'no overwrite or musical-quality claim' is grammatically compressed to the point of slight ambiguity, costing it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 10-parameter export with an output schema present, the description covers preconditions, side effects on export preferences, and known limitations. The one material omission is the dryRun/planHash/confirmationToken two-step execution model, which an agent must reconstruct from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so path, start, length, bitDepth, sampleRate and the concurrency fields are already described; the description's mention of verifying 'native settings and file format' loosely ties to bitDepth/sampleRate. The most consequential parameters — planHash, confirmationToken and dryRun, i.e., the plan-then-confirm two-phase flow — are never explained in the description, so it adds only marginal meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'Export Main as stereo WAV,' which distinguishes it from track- and clip-level exports by naming the Master bus and the stereo/WAV output. It does not name any sibling (e.g., export_audio_track) explicitly, so the agent must infer the boundary from the object ('Main').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a concrete use gate: 'Requires stopped transport, recording off, unarmed tracks and an absent destination,' which tells the agent the session conditions that must hold before calling. It stops short of naming an alternative tool or saying what to do when the destination already exists, so the agent must derive the fallback on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server