Ableton Live + mcp-agent: Complete MCP Integration
Ableton Live is a MCP server that an MCP server to control Ableton Live..
When integrated with mcp-agent, 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-agent, 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-agent
- 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-agent installed and configured
- Compatible operating system (Python 3.9+, pip Installation, uv Installation, Temporal (Optional))
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-agent
- Open mcp-agent 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-agent:
Prepare Recording Setup
Set up tracks for recording a rock band
Ask mcp-agent: "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-agent: "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-agent: "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-agent: "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-agent
- 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
Import Error - Module Not Found
Symptoms: ModuleNotFoundError: No module named mcp_agent, Import fails
Cause: mcp-agent not installed or wrong Python environment
Solution:
- Verify installation: pip show mcp-agent
- Ensure using correct Python environment/virtualenv
- Reinstall: pip install --upgrade mcp-agent
- Check Python version is 3.9 or higher
MCP Server Connection Failures
Symptoms: Server not starting, Connection timeout, Tool execution errors
Cause: Invalid MCP server configuration or missing dependencies
Solution:
- Verify npx is installed and accessible (required for stdio servers)
- Check MCP server package name and arguments are correct
- Test server independently: npx -y @modelcontextprotocol/server-filesystem /path
- Review agent logs for detailed error messages
- Ensure required environment variables are set
LLM API Authentication Errors
Symptoms: 401 Unauthorized, API key invalid, Provider authentication failed
Cause: Missing or incorrect API keys for LLM provider
Solution:
- Set environment variables: ANTHROPIC_API_KEY, OPENAI_API_KEY, etc.
- Verify API key is valid and has correct permissions
- Check API key format matches provider requirements
- Pass api_key parameter explicitly in Agent initialization
Workflow Execution Failures
Symptoms: Workflow hangs, Timeout errors, Incomplete results
Cause: Workflow pattern misconfiguration or task complexity
Solution:
- Increase timeout values for long-running tasks
- Break complex workflows into smaller steps
- Verify all workflow dependencies are available
- Check Temporal backend is running (for production deployments)
- Review workflow logs for specific error messages
Temporal Backend Connection Issues
Symptoms: Cannot connect to Temporal, Workflow registration fails, Worker errors
Cause: Temporal server not running or misconfigured
Solution:
- Verify Temporal server is running: temporal server health
- Check Temporal connection settings (host, port, namespace)
- Ensure Temporal workers are registered correctly
- Review Temporal server logs for connection errors
- Start local Temporal dev server: temporal server start-dev
Performance Issues with Large Workflows
Symptoms: Slow execution, High memory usage, Timeout errors
Cause: Inefficient workflow design or resource constraints
Solution:
- Use map-reduce pattern for parallelizable tasks
- Implement batching for large data processing
- Enable Temporal backend for better resource management
- Monitor agent memory usage and optimize task size
- Consider streaming responses for large outputs
Ableton Live not appearing in mcp-agent
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Ableton Live installation
- Restart mcp-agent
- Check logs for error messages
Next Steps
Now that Ableton Live is integrated with mcp-agent:
- Explore all Ableton Live capabilities through mcp-agent
- Check out other MCP servers that work with mcp-agent
- Join the MCP community for tips and support
- Consider contributing to Ableton Live development
Need Help?
- Search for Ableton Live documentation
- Check the mcp-agent MCP guide
- Join the MCP community discussions