Skip to main content
mcpSource-backed

Ableton MCP Extended

Source-install MCP server for controlling Ableton Live from Claude, including session inspection, track and clip creation, MIDI note editing, tempo and transport control, browser item loading, arrangement workflows, device parameters, automation, external plugins, audio imports, and optional ElevenLabs.

by uisato · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/uisato/ableton-mcp-extended/blob/main/README.md, https://github.com/uisato/ableton-mcp-extended
Brand
Ableton MCP Extended
Brand domain
github.com
Safety notes
Ableton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content., Device and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound., Automation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving., The Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished., Voice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.
Privacy notes
Live Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model., Optional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API., Local logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans., Keep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.
Author
uisato
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

25 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/6 ready
Account & credentials1Install & runtime1Review & approval1General325 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.

5 areas
  • SafetyGeneralAbleton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content.
  • SafetyGeneralDevice and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound.
  • SafetyCredentials & tokensAutomation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving.
  • SafetyNetwork accessThe Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished.
  • SafetyThird-party handlingVoice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.
  • PrivacyThird-party handlingLive Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model.
  • PrivacyNetwork accessOptional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API.
  • PrivacyLocal filesLocal logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans.
  • PrivacyCredentials & tokensKeep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.

Safety notes

  • Ableton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content.
  • Device and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound.
  • Automation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving.
  • The Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished.
  • Voice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.

Privacy notes

  • Live Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model.
  • Optional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API.
  • Local logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans.
  • Keep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.

Prerequisites

  • Ableton Live 11 or newer.
  • Python 3.10 or newer and pip for the source-install MCP server.
  • Git for cloning the source repository.
  • The AbletonMCP Remote Script copied into Ableton Live's User Remote Scripts directory and selected as a control surface.
  • An approved Live Set backup before Claude edits tracks, clips, notes, devices, automation, arrangement clips, cue points, or plugins.
  • Optional ElevenLabs API key and approved audio output directory when using the bundled voice-generation workflows.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
25 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "AbletonMCP": {
      "command": "python",
      "args": ["<path-to-ableton-mcp-extended/MCP_Server/server.py>"]
    }
  }
}

About this resource

Content

Ableton MCP Extended is a source-install Model Context Protocol server for controlling Ableton Live from Claude and other MCP clients. It pairs a Python MCP server with an Ableton Remote Script so model-driven tool calls can inspect a Live Set and perform track, clip, MIDI, device, browser, arrangement, transport, automation, plugin, and audio-import actions.

The project extends the original Ableton MCP idea with a larger tool surface, optional high-performance UDP examples, and bundled ElevenLabs integration for voice or sound-effect generation workflows. It is a community project and is not an official Ableton product.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, installation guide, Python package metadata, MCP server, Ableton Remote Script, environment template, UDP example source, and license file for current setup requirements, tool behavior, local socket behavior, optional credentials, and licensing.

Features

  • Python MCP server for Ableton Live control through a local Remote Script.
  • Ableton Remote Script that listens for MCP-server commands and executes them through the Live API.
  • Session and transport tools for session info, tempo, playback, clip firing, stopping, song time, cue points, loop ranges, and view controls.
  • Track, clip, and MIDI workflows for creating tracks, naming tracks, adjusting volume and pan, creating clips, adding notes, naming clips, and manipulating arrangement clips.
  • Browser, instrument, effect, sample, plugin, and preset workflows for loading devices or audio into the Live Set.
  • Device and automation workflows for reading parameters, setting normalized parameter values, enabling or disabling devices, deleting devices, and managing clip automation.
  • Optional ElevenLabs integration and audio output configuration for generated voice or sound-effect imports.
  • MIT license.

Installation

Clone and install the source project:

git clone https://github.com/uisato/ableton-mcp-extended.git
cd ableton-mcp-extended
pip install -e .

Copy the Ableton Remote Script into Live's User Remote Scripts folder, select AbletonMCP as a control surface in Ableton Live, then configure the MCP client:

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "python",
      "args": ["<path-to-ableton-mcp-extended/MCP_Server/server.py>"]
    }
  }
}

Restart the MCP client and open Ableton Live with a backed-up or disposable Live Set before testing write-capable commands.

Use Cases

  • Ask Claude to summarize the tracks, clips, tempo, devices, and arrangement state of an approved Live Set.
  • Create MIDI or audio tracks, clips, notes, and arrangement sections from a structured production prompt.
  • Load instruments, effects, plugins, presets, or samples while sketching an arrangement.
  • Adjust volume, pan, tempo, loop ranges, cue points, and device parameters during a supervised production session.
  • Generate or import spoken-word, narration, or sound-effect audio with an approved ElevenLabs key and output folder.
  • Prototype Live performance controllers or low-latency parameter workflows with the optional UDP examples.

Safety and Privacy

Ableton MCP Extended is write-capable DAW control software. Use it first with copies of Live Sets and keep a human producer in the loop before saving, rendering, performing, or sending project files. Claude can trigger playback, change tempo, fire clips, create or delete content, alter device parameters, load plugins, import files, and modify arrangement or automation state.

The Remote Script opens a local socket server inside Ableton Live. Keep that server available only to trusted local clients, avoid running it on untrusted networks, and remove or disable the control surface when you no longer need MCP control. Review generated clips, automation, device changes, and imported audio before committing changes to an important Live Set.

Live Set structure, track names, plugin names, sample paths, MIDI notes, cue points, generated voice prompts, and model conversations can reveal unreleased music, client material, commercial sample libraries, or performance plans. Protect ElevenLabs API keys, generated audio folders, logs, screenshots, and MCP client configuration as project-sensitive data.

Duplicate Check

No Ableton MCP Extended, uisato/ableton-mcp-extended, Ableton Live MCP, DAW MCP, or dedicated Ableton MCP entry was found in content/mcp, content/agents, content/guides, or content/skills. This entry is scoped to the community Ableton MCP Extended source project and does not duplicate Max/MSP or other creative-coding MCP entries.

Source citations

Add this badge to your README

Show that Ableton MCP Extended is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/ableton-mcp-extended.svg)](https://heyclau.de/entry/mcp/ableton-mcp-extended)

How it compares

Ableton MCP Extended side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Source-install MCP server for controlling Ableton Live from Claude, including session inspection, track and clip creation, MIDI note editing, tempo and transport control, browser item loading, arrangement workflows, device parameters, automation, external plugins, audio imports, and optional ElevenLabs.

Open dossier

Source-install MCP server that connects Claude to Max, Max/MSP, and Jitter patches so it can inspect patch objects, add and remove objects, connect and disconnect patch cords, set attributes, send messages, trigger bangs, and use bundled Max object documentation while building or explaining patches.

Open dossier

MCP server for controlling DaVinci Resolve Studio through the official scripting API, with tools for projects, timelines, media pools, render setup, review markers, grading, Fusion, Fairlight, and source-safe media analysis.

Open dossier

Official ElevenLabs MCP server for generating speech, designing voices, cloning voices, transcribing audio, creating sound effects, and working with conversational audio agents through the ElevenLabs API.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandDaVinci Resolve MCP Server logoDaVinci Resolve MCP ServerElevenLabs MCP Server logoElevenLabs MCP Server
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthoruisatoHaokun Tian and Shuoyang ZhengSamuel GurskyElevenLabs
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesAbleton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content. Device and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound. Automation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving. The Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished. Voice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.MaxMSP MCP Server can add and remove Max objects, connect and disconnect patch cords, set object attributes, change message text, set number boxes, and send messages or bangs to named objects. These actions can alter a patch, trigger audio or visual behavior, destabilize a live performance patch, or change saved creative work if used on an important project. The Max-side bridge starts a Socket.IO server inside Max with permissive CORS in the reviewed source, so keep it bound to trusted local workflows and avoid exposing it to untrusted networks. The installer writes MCP client configuration files, so review paths and generated config before running it on shared or managed machines. The setup installs Python and npm dependencies from the source project; review dependency manifests before installing or running the bridge.DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs. Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts. Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives. The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only. Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders. Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.ElevenLabs MCP Server can call paid ElevenLabs API endpoints; text-to-speech, voice design, voice cloning, audio isolation, transcription, sound generation, music, and agent workflows can consume account credits. Voice cloning and voice conversion can create realistic synthetic speech, so require documented consent and review before processing a person's voice or publishing generated audio. Generated speech, sound effects, music, transcripts, and conversation-agent configuration can affect public-facing content; review prompts, voice IDs, output format, language, and destination before publishing or sending. File output mode writes generated files to disk under the configured base path; restrict that path to an approved directory and avoid broad home, desktop, or shared folders in production. Use separate API keys or workspaces for test and production clients, monitor credit usage, and disable tools in clients that should not spend credits. Some operations may take longer than normal MCP tool timeouts; do not retry expensive generation calls blindly.
Privacy notesLive Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model. Optional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API. Local logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans. Keep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.Patch object names, arguments, comments, selected objects, subpatch structure, and generated Max documentation context can be sent to the MCP client and model. Prompts and transcripts can reveal unreleased music, audiovisual systems, installation designs, performance patches, plugin ideas, or teaching material. Socket.IO traffic between the Python server and Max can carry patch structure and command payloads, so keep the bridge on trusted local interfaces. Back up patches and avoid exposing proprietary samples, cue logic, show-control data, or private project notes through the MCP session.Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client. Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details. Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider. Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings. Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.The MCP client can expose ElevenLabs API keys, voice IDs, text prompts, voice descriptions, uploaded audio samples, generated audio paths, transcripts, diarized speaker labels, and conversational-agent settings. Uploaded audio and generated outputs may contain biometric voice characteristics, names, background sounds, private conversations, or copyrighted material. File, resource, and both output modes can retain generated audio locally, in MCP resources, in logs, or in chat transcripts depending on the client. Treat voice samples and transcripts as sensitive data, and delete generated files or cached resources when they are no longer needed. Review ElevenLabs account, retention, residency, and enterprise data-residency settings before using the server with regulated or customer data.
Prerequisites
  • Ableton Live 11 or newer.
  • Python 3.10 or newer and pip for the source-install MCP server.
  • Git for cloning the source repository.
  • The AbletonMCP Remote Script copied into Ableton Live's User Remote Scripts directory and selected as a control surface.
  • Python 3.8 or newer, uv, and the Python MCP CLI available to the configured MCP client.
  • Max 9 or newer, according to the upstream README.
  • npm available inside Max for the bundled MaxMSP_Agent bridge dependencies.
  • A cloned copy of the source repository and the MaxMSP_Agent bridge installed in the patch you want Claude to inspect or edit.
  • DaVinci Resolve Studio 18.5 or newer; the free edition does not support the required external scripting API.
  • Resolve external scripting set to `Local`.
  • Python 3.10 or newer, with Python 3.10-3.12 recommended for the broadest Resolve compatibility.
  • A local MCP client that can launch stdio servers under the same user account that operates Resolve.
  • Python 3.11 or newer with `uvx` available.
  • An ElevenLabs API key for the account and workspace you intend Claude to use.
  • Review of ElevenLabs pricing, credits, voice-cloning policy, content rules, and data handling before enabling tools that generate or process audio.
  • An approved output directory when using file-based generated audio output.
Install
git clone https://github.com/uisato/ableton-mcp-extended.git && cd ableton-mcp-extended && pip install -e .
git clone https://github.com/tiianhk/MaxMSP-MCP-Server.git && cd MaxMSP-MCP-Server && uv venv && uv pip install -r requirements.txt
npx davinci-resolve-mcp setup
uvx elevenlabs-mcp
Config
{
  "mcpServers": {
    "AbletonMCP": {
      "command": "python",
      "args": ["<path-to-ableton-mcp-extended/MCP_Server/server.py>"],
      "env": {
        "ELEVENLABS_API_KEY": "",
        "ELEVENLABS_OUTPUT_DIR": "<approved-ableton-audio-output-directory>"
      }
    }
  }
}
{
  "mcpServers": {
    "MaxMSPMCP": {
      "command": "mcp",
      "args": ["run", "<path-to-MaxMSP-MCP-Server/server.py>"],
      "env": {
        "SOCKETIO_SERVER_URL": "<socketio-server-url>",
        "SOCKETIO_SERVER_PORT": "<socketio-server-port>",
        "NAMESPACE": "<socketio-namespace>"
      }
    }
  }
}
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "npx",
      "args": [
        "davinci-resolve-mcp",
        "server"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
claude mcp add elevenlabs --env ELEVENLABS_API_KEY=YOUR_ELEVENLABS_API_KEY -- uvx elevenlabs-mcp
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.