Ableton Live + GitHub Copilot (VS Code): Complete MCP Integration

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

When integrated with GitHub Copilot (VS Code), 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 GitHub Copilot (VS Code), 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 GitHub Copilot (VS Code)
• 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
• GitHub Copilot (VS Code) installed and configured
• Compatible operating system (Windows, macOS, Linux)

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 GitHub Copilot (VS Code)

1. Locate your configuration file:

   • Windows: .vscode\\mcp.json in your project directory
   • macOS: .vscode/mcp.json in your project directory
   • Linux: .vscode/mcp.json in your project directory

2. Add server configuration:

{
  "mcpServers": {
    "ableton-live": {
      "command": "ableton live",
      "args": [],
      "env": {
        
      }
    }
  }
}

3. Restart GitHub Copilot (VS Code)

Completely quit and restart GitHub Copilot (VS Code) to load the new configuration.

Examples

Once configured, you can use Ableton Live in GitHub Copilot (VS Code):

Prepare Recording Setup

Set up tracks for recording a rock band

Ask GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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. Start a new conversation in GitHub Copilot (VS Code)
2. Ask GitHub Copilot (VS Code) to list available tools
3. Try using Ableton Live functionality

Test prompts:

• "What MCP tools are available?"
• "Use Ableton Live to help with my code"
• "Show me what Ableton Live can do"

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

MCP Configuration Not Loaded

Symptoms: MCP tools not appearing, Copilot does not recognize MCP server

Cause: Configuration file not in correct location or invalid JSON

Solution:

• Verify .vscode/mcp.json exists in project root directory
• Check JSON syntax is valid (no trailing commas, proper quotes)
• Reload VS Code window after making configuration changes
• Check VS Code Developer Tools (Help > Toggle Developer Tools) for errors

MCP Server Not Starting

Symptoms: Tools listed but not responding, Server connection errors

Cause: Server command path incorrect or dependencies missing

Solution:

• Test the MCP server command independently in terminal
• Verify all server prerequisites are installed
• Check that command path is correct (use absolute paths if needed)
• Ensure required environment variables are set in mcp.json
• Review VS Code Output panel for MCP server error messages

GitHub Copilot Subscription Required

Symptoms: Copilot features grayed out, Unable to access Copilot Chat

Cause: No active GitHub Copilot subscription

Solution:

• Sign up for GitHub Copilot subscription (Individual, Business, or Enterprise)
• Verify subscription is active in GitHub account settings
• Re-authenticate GitHub Copilot in VS Code
• Check that VS Code is using correct GitHub account

VS Code Version Too Old

Symptoms: MCP configuration ignored, No mcp.json recognition

Cause: VS Code version below 1.99 does not have native MCP support

Solution:

• Update VS Code to version 1.99 or later
• Check current version: Help > About
• Download latest version from code.visualstudio.com
• After updating, reload window and verify MCP support

{server_name} Tools Not Working

Symptoms: Server connected but tools fail, Error messages when invoking tools

Cause: Server-specific configuration or authentication issues

Solution:

• Verify all required environment variables for {server_name} are set
• Check {server_name} documentation for specific prerequisites
• Test {server_name} with another MCP client to isolate issue
• Review error messages in VS Code Output panel for specific failures

Ableton Live not appearing in GitHub Copilot (VS Code)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Ableton Live installation
• Restart GitHub Copilot (VS Code)
• Check logs for error messages

Next Steps

Now that Ableton Live is integrated with GitHub Copilot (VS Code):

• Explore all Ableton Live capabilities through GitHub Copilot (VS Code)
• Check out other MCP servers that work with GitHub Copilot (VS Code)
• Join the MCP community for tips and support
• Consider contributing to Ableton Live development

Need Help?

• Search for Ableton Live documentation
• Check the GitHub Copilot (VS Code) MCP guide
• Join the MCP community discussions