Ableton Live + MCPHub (mcp.nvim): Complete MCP Integration
Ableton Live is a MCP server that an MCP server to control Ableton Live..
When integrated with MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim)
- 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
- MCPHub (mcp.nvim) installed and configured
- Compatible operating system (Neovim 0.9+, Windows, macOS, Linux)
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 MCPHub (mcp.nvim)
- Open MCPHub (mcp.nvim) 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 MCPHub (mcp.nvim):
Prepare Recording Setup
Set up tracks for recording a rock band
Ask MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim)
- 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
Plugin Not Loading or Command Not Found
Symptoms: :MCPHub command not recognized, Plugin not appearing in :PlugStatus, No errors but plugin inactive
Cause: Plugin not properly installed or configuration error
Solution:
- Verify plugin is added to plugin manager configuration
- Run plugin manager install command (:PackerInstall, :PlugInstall, or Lazy auto-install)
- Check for errors in :messages after sourcing config
- Ensure dependencies (plenary.nvim, nui.nvim) are installed
- Restart Neovim completely
MCP Server Won't Start
Symptoms: Server status shows "Error", Red indicator on server, Server immediately stops after starting
Cause: Invalid server configuration or missing dependencies
Solution:
- Verify npx is installed and in PATH: npx --version
- Check MCP server package exists: npx -y @modelcontextprotocol/server-filesystem --help
- Review server configuration in setup() - verify command and args
- Check server logs in MCPHub interface for detailed error messages
- Ensure required environment variables are set (e.g., GITHUB_TOKEN)
- Test server manually in terminal: npx -y @modelcontextprotocol/server-filesystem /path
UI Not Displaying Correctly
Symptoms: Blank window, Garbled text, Layout issues, Missing borders
Cause: Terminal or Neovim rendering issues
Solution:
- Verify Neovim version is 0.9 or higher: nvim --version
- Try different border style in ui.border config ("single", "double", "rounded")
- Check terminal supports Unicode and 256 colors
- Update nui.nvim dependency to latest version
- Test with different colorscheme to rule out theme conflicts
Integration with Avante/CodeCompanion Not Working
Symptoms: AI assistant not seeing MCP tools, Tool calls failing, Integration not recognized
Cause: Integration not enabled or incompatible versions
Solution:
- Verify integration is enabled in config: integrations.avante = true
- Ensure Avante.nvim/CodeCompanion.nvim is installed and loaded
- Check versions are compatible - update both plugins to latest
- Restart Neovim after enabling integration
- Check :checkhealth for integration-specific warnings
Marketplace Not Loading
Symptoms: :MCPHubMarketplace shows empty list, Network error in marketplace, Timeout loading servers
Cause: Network connectivity issues or marketplace service unavailable
Solution:
- Verify internet connectivity
- Check firewall allows HTTPS connections
- Try again later if marketplace service is temporarily down
- Review proxy settings if behind corporate firewall
- Check :messages for detailed network error messages
Project-Local Config Not Loading
Symptoms: .mcphub.json ignored, Project servers not appearing, Only global config loaded
Cause: Config file location or format issues
Solution:
- Verify .mcphub.json is in project root (same directory as .git)
- Check JSON syntax is valid using jsonlint or similar tool
- Ensure file name is exactly .mcphub.json (case-sensitive)
- Restart Neovim after creating/modifying project config
- Check file permissions are readable
Ableton Live not appearing in MCPHub (mcp.nvim)
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Ableton Live installation
- Restart MCPHub (mcp.nvim)
- Check logs for error messages
Next Steps
Now that Ableton Live is integrated with MCPHub (mcp.nvim):
- Explore all Ableton Live capabilities through MCPHub (mcp.nvim)
- Check out other MCP servers that work with MCPHub (mcp.nvim)
- Join the MCP community for tips and support
- Consider contributing to Ableton Live development
Need Help?
- Search for Ableton Live documentation
- Check the MCPHub (mcp.nvim) MCP guide
- Join the MCP community discussions