Skip to main content
Glama
romanstark

Live Maestro

by romanstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Live Maestro

  • Dorico Maestro

    romanstark
    A
    license
    A
    quality
    A
    maintenance
    An AI composition partner that remote-controls Steinberg Dorico through the Model Context Protocol, enabling composers to create, edit, play back, and refine musical scores using natural language.
    30
    2
    AGPL 3.0

Related Servers

  • LivePilot

    dreamrec
    A
    license
    Not graded
    quality
    A
    maintenance
    AI copilot for Ableton Live 12 — 104 MCP tools for music production, sound design, and mixing. Talk to your DAW. Create tracks, program MIDI, load instruments, tweak parameters, arrange songs, and mix — all through natural language. LivePilot connects any MCP-compatible AI client (Claude, Cursor, VS Code Copilot) to Ableton Live and gives it full control over your session.
    402 npm
    83
    Business Source 1.1

  • Ableton DJ MCP

    gpulga
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI-assisted electronic music production in Ableton Live, with built-in genre theory for indie dance, tech house, melodic techno, and house music.
    6
    GPL 3.0

  • Ableton MCP

    keigotak
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables natural language control over Ableton Live for generating musical patterns, melodies, and full song arrangements. It also provides tools for sample searching and mixing assistance through an OSC-based connection with Claude Desktop.
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 60 tools

Disambiguation3/5

The set includes several overlapping pairs such as describe/lom_describe, set_parameter/set_parameter_display/lom_set, and get_session/get_set_state, so an agent must rely on lengthy notes to choose correctly. Most tools do target distinct resources and actions, but the overlap prevents fully clean selection.

Naming Consistency4/5

Tool names are consistently snake_case and mostly follow verb_noun conventions; families like lom_* and als_* add prefixes but remain predictable. A few bare verbs (play, stop, arrange, describe) and the noun-phrase sound_index_status are minor deviations.

Tool Count1/5

60 tools is far beyond the typical 3–15 well-scoped range and qualifies as an extreme over-scoping mismatch. Many tempo, audio, LOM, and automation operations could be consolidated without losing coverage.

Completeness4/5

The surface covers core Ableton workflows: session/track/clip/device CRUD, note editing, automation, tempo/warp, mixing, arrangement, audio analysis, and library search. Some lifecycle operations like renaming, rendering/export, and explicit scene management are absent, but generic LOM calls provide workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources