Ableton Mcp Lofifren

What is Ableton Mcp Lofifren?

Ableton Mcp Lofifren connects Ableton Live to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted music production, track creation, and Live session manipulation. It is a fork of ahujasid/ableton-mcp that adds ~35 additional MCP tools and a 33-personality rule-based style system.

How to use Ableton Mcp Lofifren?

Install the package from PyPI with pip install ableton-mcp-lofifren or run it directly using uvx ableton-mcp-lofifren. Configure it as an MCP server in Claude Desktop, Cursor, or VS Code using the provided install buttons; then connect it to a running Ableton Live session.

Key features of Ableton Mcp Lofifren

• 33 rule-based player personalities (Coltrane, Bill Evans, Dilla, Metro Boomin, etc.)
• ~35 additional MCP tools across six tiers
• Bootstrap a full session with one call (setup_session)
• Composite tools: create_clip_with_notes, duplicate_clip, create_track
• Musical helpers: chord progressions, scale runs, drum patterns, quantization
• Personality blending via add_blended_personality_solo
• Arrangement view support (BETA): locators, loop, timeline clip placement

Use cases of Ableton Mcp Lofifren

• Generate a Coltrane-style solo or Bill Evans comping over a chord progression
• Build a complete song structure with a single prompt (session, tracks, clips, arrangements)
• Create genre-specific drum patterns (trap, boom bap, breakbeat, four-on-the-floor)
• Blend two player personalities for unique hybrid solos (e.g., 70% Coltrane + 30% Kenny G)
• Speed up music production workflows by controlling Ableton Live from natural language

FAQ from Ableton Mcp Lofifren

What is the difference between this fork and the original ahujasid/ableton-mcp?

This fork adds ~35 additional MCP tools (session scaffolding, clip editing, mixer controls, browser improvements, musical helpers) and a 33-personality style system. It is published on PyPI as ableton-mcp-lofifren.

What dependencies does Ableton Mcp Lofifren require?

It requires a running instance of Ableton Live (tested on Live 12.2.7 for arrangement features) and an MCP client that supports the Model Context Protocol (e.g., Claude Desktop, Cursor, VS Code).

Where does my session data live?

All data stays within your local Ableton Live session. The MCP server only reads/writes Live’s internal state; no audio or MIDI data is sent externally.

Is the arrangement view feature stable?

Arrangement view tools are labelled BETA. set_arrangement_loop and add_arrangement_locator are stable on Live 11+, but add_clip_to_arrangement is verified on Live 12.2.7 and may return an unsupported error on older versions.

What transports or authentication does this MCP server use?

The server communicates with the MCP client via standard stdio transport (uvx). No authentication is required—it assumes a local, trusted Ableton Live instance.