How ahujasid/ableton-mcp works
Project type and purpose
• This is an integration tool (open‑source plugin) that connects Ableton Live (via a MIDI Remote Script) to Claude AI using the Model Context Protocol (MCP).
• Purpose: allow Claude AI to send commands (create tracks, clips, control transport, load devices) to Ableton Live and receive session information back.
File structure
• Top‑level artifacts:
• AbletonMCP_Remote_Script/ – contains the Ableton Live MIDI Remote Script (__init__.py)
• MCP_Server/ – contains the Python MCP server (server.py)
• Dockerfile, pyproject.toml, smithery.yaml – build/deployment/configuration files
• No “frontend” or “backend” folders; instead two collaborating components: a client (the Remote Script) and the server (the Python MCP implementation).
• Configuration files indicate packaging for uv (uv.lock), Python dependency management (pyproject.toml), and Docker (Dockerfile).
Key insights from the README
• Two‑way JSON‑over‑TCP communication between Remote Script and MCP Server.
• The MCP Server is launched via uvx (the uv package manager) from Claude Desktop or Cursor.
• The Remote Script lives inside Ableton’s “MIDI Remote Scripts” directory and opens a socket to listen for commands from the MCP Server.
• The MCP Server implements MCP to translate Claude AI requests into JSON commands and send them to the Remote Script.
Main components
a. Ableton Live Application
• Loads the MIDI Remote Script plugin (AbletonMCP_Remote_Script).
• Exposes a socket endpoint for JSON commands (port X).
b. AbletonMCP Remote Script
• Connects inside Ableton Live, implements socket client/server for JSON messages.
• Translates JSON commands into Ableton Live API calls (track/clip manipulation, transport control).
c. MCP Server (Python)
• Listens on TCP for Remote Script connections.
• Implements Model Context Protocol to accept commands from Claude.
• Translates Claude MCP requests into JSON commands for the Remote Script, and returns JSON responses.
d. Claude Desktop / Cursor Client
• Launches the MCP Server via uvx (defined in claude_desktop_config.json).
• Sends MCP messages to the server when the user interacts with the AI.
e. External Dependencies
• Python 3.8+, uv (uv package manager), TCP/IP networking.
• Docker (optional) for containerized deployment.
Relationships and interactions
• Claude UI → MCP Server: sends MCP commands over standard IO (uvx) or socket.
• MCP Server ↔ Ableton Remote Script: bidirectional JSON over TCP socket.
• Ableton Remote Script → Ableton Live API: internal calls to manipulate tracks, clips, transport.
• MCP Server → Claude: returns status and results via MCP protocol.
Architectural patterns and design principles
• Plugin architecture: Ableton Remote Script plugs into Live.
• Client‑server pattern: Remote Script and MCP Server communicate over TCP.
• Protocol translation: MCP Server translates between MCP and JSON socket protocol.
• Separation of concerns: UI/CLI launch (uvx), protocol layer (MCP), domain logic (Ableton API calls).
Detail without over‑complication
• Port numbers if known.
• Where configuration files live (e.g., claude_desktop_config.json entry).
• Call out build/runtime steps (e.g., “uvx ableton-mcp” launch).
• Essential components and their interactions—more granular separation is better than lumping everything together.