beginner⏱️ 20-30 minutes📅 Updated August 2026

Step-by-step guide to integrate Ableton Live MCP server with mcp-use. Includes track management and live performance control.

Ableton Live + mcp-use: Complete MCP Integration

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

When integrated with mcp-use, 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-use, 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-use
  • 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-use installed and configured
  • Compatible operating system (Python 3.8+, Node.js 16+, pip Installation, npm/yarn Installation)

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 mcp-use

  1. Open mcp-use 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 mcp-use:

Prepare Recording Setup

Set up tracks for recording a rock band

Ask mcp-use: "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-use: "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-use: "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-use: "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 mcp-use
  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

Connection Refused or Server Unreachable

Symptoms: ECONNREFUSED error, Connection timeout, Cannot reach server

Cause: MCP server not running or incorrect URL

Solution:

  • Verify MCP server is running and accessible
  • Check server URL is correct (protocol, host, port, path)
  • Test server URL in browser or with curl to confirm it responds
  • Ensure firewall allows connections to server port
  • Verify CORS settings if accessing from browser

Import Errors or Module Not Found

Symptoms: ModuleNotFoundError: mcp_use, Cannot find module "mcp-use"

Cause: Package not installed or wrong environment

Solution:

  • Verify installation: pip show mcp-use (Python) or npm list mcp-use (JS)
  • Ensure using correct Python virtual environment or Node.js project
  • Reinstall package: pip install --upgrade mcp-use or npm install mcp-use
  • Check package.json or requirements.txt includes mcp-use

Tool Discovery Returns Empty List

Symptoms: list_tools() returns [], No tools available, Tools not found

Cause: MCP server not properly configured or not exposing tools

Solution:

  • Verify MCP server is properly initialized and configured
  • Check server logs to confirm tools are registered
  • Test server directly with MCP inspector or test client
  • Ensure server implements MCP protocol correctly
  • Verify transport type (HTTP/SSE) matches server configuration

Tool Execution Fails or Returns Errors

Symptoms: Tool call throws exception, Invalid arguments error, Execution timeout

Cause: Incorrect arguments or server-side execution failure

Solution:

  • Verify tool arguments match schema definition from list_tools()
  • Check required arguments are provided with correct types
  • Review server logs for detailed error messages
  • Test tool with minimal valid arguments first
  • Increase timeout if tool requires longer execution time

LangChain.js Integration Not Working

Symptoms: getLangChainTools() fails, Tools not recognized by agent, Type errors

Cause: Version mismatch or incorrect integration setup

Solution:

  • Ensure LangChain.js version is compatible with mcp-use
  • Verify TypeScript version meets requirements
  • Check tool schema conversion is working correctly
  • Use latest versions of both mcp-use and LangChain.js
  • Review LangChain.js documentation for agent setup

Transport Type Errors (HTTP vs SSE)

Symptoms: SSE connection fails, HTTP polling not working, Event stream errors

Cause: Mismatch between client transport and server capabilities

Solution:

  • Verify server supports the transport type you are using
  • Try alternative transport: switch between "http" and "sse"
  • Check server documentation for supported transport types
  • For SSE, ensure server sends proper Content-Type: text/event-stream
  • For HTTP, verify server accepts POST requests with JSON payload

Ableton Live not appearing in mcp-use

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check Ableton Live installation
  • Restart mcp-use
  • Check logs for error messages

Next Steps

Now that Ableton Live is integrated with mcp-use:

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

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with mcp-use

Need Help?

Join the MCP community for support and discussions

Ableton Live + mcp-use: MCP Setup Guide (2026)