Ableton Live + MCP Inspector: Complete MCP Integration
Ableton Live is a MCP server that an MCP server to control Ableton Live..
When integrated with MCP Inspector, 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 MCP Inspector, 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 MCP Inspector
- 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
- MCP Inspector installed and configured
- Compatible operating system (CLI Tool)
Installation
Step 1: Install Ableton Live
Manual installation steps:
- Install Python 3.8 or higher
- Install uv package manager
- Clone repository: git clone https://github.com/Simon-Kansara/ableton-live-mcp-server.git
- Navigate to project: cd mcp_ableton_server
- Install dependencies: uv sync
Configuration
Step 2: Configure MCP Inspector
- Open MCP Inspector settings
- Navigate to MCP server configuration
- Add Ableton Live server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use Ableton Live in MCP Inspector:
Prepare Recording Setup
Set up tracks for recording a rock band
Ask MCP Inspector: "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 MCP Inspector: "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 MCP Inspector: "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 MCP Inspector: "Start recording on track 3 and set tempo to 120 BPM"
Expected Result: Recording initiated on specified track with tempo adjusted
Testing Your Setup
- Launch MCP Inspector
- Verify Ableton Live is available in the tools list
- 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
Connection Failed
Symptoms: Inspector UI shows "Disconnected"
Cause: Server process exited or failed to start.
Solution:
- Check the terminal where you ran
npx ...for error output from your server. - Ensure your server prints JSON-RPC messages to
stdout.
Tools Not Showing
Symptoms: Tool list is empty
Cause: Server did not send tools/list response or capabilities negotiation failed.
Solution:
- Check the "Console" or "Logs" tab in the Inspector to see the raw communication.
- Verify your server code correctly implements the
ListToolsRequesthandler.
Ableton Live not appearing in MCP Inspector
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Ableton Live installation
- Restart MCP Inspector
- Check logs for error messages
Next Steps
Now that Ableton Live is integrated with MCP Inspector:
- Explore all Ableton Live capabilities through MCP Inspector
- Check out other MCP servers that work with MCP Inspector
- Join the MCP community for tips and support
- Consider contributing to Ableton Live development
Need Help?
- Search for Ableton Live documentation
- Check the MCP Inspector MCP guide
- Join the MCP community discussions