Ableton Live + OpenSumi: Complete MCP Integration

Ableton Live is a MCP server that an MCP server to control Ableton Live..

When integrated with OpenSumi, you can:

• Create, modify, and control audio/MIDI tracks
• Control live performance parameters and session view
• Send and receive OSC messages for real-time control

This guide provides step-by-step instructions to set up Ableton Live in OpenSumi, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Ableton Live will be fully integrated and operational
• You can use Ableton Live tools directly in OpenSumi
• All Ableton Live capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• Python 3.8+
• Git
• Ableton Live installed
• OpenSumi installed and configured
• Compatible operating system (Web (Browser-based), Electron Desktop, Container (Docker/K8s), Framework Integration)

Installation

Step 1: Install Ableton Live

Manual installation steps:

1. Install Python 3.8 or higher
2. Install uv package manager
3. Clone repository: git clone https://github.com/Simon-Kansara/ableton-live-mcp-server.git
4. Navigate to project: cd mcp_ableton_server
5. Install dependencies: uv sync

Configuration

Step 2: Configure OpenSumi

1. Open OpenSumi settings
2. Navigate to MCP server configuration
3. Add Ableton Live server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use Ableton Live in OpenSumi:

Prepare Recording Setup

Set up tracks for recording a rock band

Ask OpenSumi: "Prepare a set to record a rock band with drums, bass, guitar, and vocals"

Expected Result: Multiple audio tracks created with appropriate input routing and naming

Configure Voice Track Routing

Set input routing for vocal tracks

Ask OpenSumi: "Set the input routing channel of all tracks that have "voice" in their name to Ext. In 2"

Expected Result: All vocal tracks configured to receive input from external input 2

Live Performance Setup

Configure session view for live performance

Ask OpenSumi: "Set up a live performance session with 8 tracks and 16 scenes for electronic music"

Expected Result: Session view configured with tracks and scenes ready for live triggering

Transport Control

Control playback and recording

Ask OpenSumi: "Start recording on track 3 and set tempo to 120 BPM"

Expected Result: Recording initiated on specified track with tempo adjusted

Testing Your Setup

1. Launch OpenSumi
2. Verify Ableton Live is available in the tools list
3. Test basic Ableton Live functionality

Troubleshooting

Common Issues

Ableton Live Not Responding

Symptoms: OSC messages not received, No communication with Live

Cause: OSC control surface not enabled or incorrect port configuration

Solution:

• Enable AbletonOSC control surface in Live preferences
• Verify OSC ports match configuration (11000/11001)
• Restart Ableton Live after configuration changes
• Check firewall settings allow OSC communication

Port Already in Use

Symptoms: Socket binding errors, Port conflict messages

Cause: Another application using configured ports

Solution:

• Check which process is using the port: netstat -tulpn | grep :65432
• Kill conflicting process or change port in osc_daemon.py
• Use alternative ports (e.g., 65433, 11002, 11003)
• Restart both server and Ableton Live

Python Dependencies Missing

Symptoms: Import errors, Module not found errors

Cause: Required packages not installed properly

Solution:

• Run uv sync to install all dependencies
• Verify Python 3.8+ is installed: python --version
• Check virtual environment is activated
• Install missing packages manually: pip install python-osc fastmcp

OSC Messages Not Routing

Symptoms: Commands not affecting Live, No response from controls

Cause: Incorrect OSC routing or message format

Solution:

• Verify OSC address patterns match Live expectations
• Check OSC message format and data types
• Test basic OSC connectivity with simple messages
• Review osc_daemon.py configuration for routing rules

Dependency Installation Failures

Symptoms: Yarn/npm install errors, Missing packages, Version conflicts

Cause: Incompatible Node.js version or network issues

Solution:

• Ensure Node.js 16+ is installed
• Use yarn for standard installation, npm for lite version
• Clear package cache: yarn cache clean or npm cache clean --force
• Check network connectivity and proxy settings

Workspace Not Loading

Symptoms: Empty workspace, Files not showing, Permission errors

Cause: Incorrect workspace path or permissions

Solution:

• Verify MY_WORKSPACE environment variable is set correctly
• Check file system permissions for workspace directory
• Use absolute path for workspace location
• Default workspace is tools/workspace in repository

VSCode Extension Compatibility

Symptoms: Extension not loading, Extension errors, Missing features

Cause: Extension API incompatibility or missing dependencies

Solution:

• Verify extension is compatible with VSCode extension API used by OpenSumi
• Check extension documentation for known issues
• Try downloading extensions via yarn run download-extension
• Some extensions may require OpenSumi-specific adaptation

WebWorker Compilation Errors (Lite Version)

Symptoms: Compile-worker fails, Language service not working, Syntax highlighting broken

Cause: WebWorker build configuration issues

Solution:

• Run npm run compile-worker before starting
• Ensure all dependencies are installed correctly
• Check browser console for WebWorker loading errors
• Clear browser cache and rebuild

MCP Client Connection Failures

Symptoms: Cannot connect to MCP server, Tool discovery fails, MCP errors in console

Cause: MCP server not running or incorrect configuration

Solution:

• Verify MCP server is running and accessible
• Check MCP server URL in OpenSumi configuration
• Review MCP client integration code for errors
• Check browser/Electron console for detailed error messages

Electron App Not Starting

Symptoms: Electron window not opening, White screen, App crashes on launch

Cause: Electron build issues or IPC communication errors

Solution:

• Ensure Electron dependencies are installed correctly
• Check Electron version compatibility (15+)
• Review IPC communication setup in configuration
• Check Electron dev tools console for errors

Ableton Live not appearing in OpenSumi

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Ableton Live installation
• Restart OpenSumi
• Check logs for error messages

Next Steps

Now that Ableton Live is integrated with OpenSumi:

• Explore all Ableton Live capabilities through OpenSumi
• Check out other MCP servers that work with OpenSumi
• Join the MCP community for tips and support
• Consider contributing to Ableton Live development

Need Help?

• Search for Ableton Live documentation
• Check the OpenSumi MCP guide
• Join the MCP community discussions