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.
    6
    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.
    202 npm
    69
    Business Source 1.1

  • Ableton DJ MCP

    gpulga
    F
    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
    -

  • 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

A4.2/5.0

Scored across 43 tools

Disambiguation4/5

The tool set is largely distinct, with a clear layered hierarchy: get_session/get_track/get_clip/get_devices nest cleanly, and read/write pairs (notes, automation) are unambiguous. Two pairs could confuse an agent — describe vs lom_describe and set_parameter vs set_parameter_display — but the descriptions disambiguate them explicitly with cross-references, so the boundary is documented rather than left to inference.

Naming Consistency4/5

The vast majority follow a consistent verb_noun snake_case pattern (get_clip, set_tempo, create_track, delete_device, write_automation), with coherent families: set_*, get_*, read_*/write_*, create_*/delete_*, and a clearly prefixed lom_* raw layer. Minor deviations are the bare verbs arrange, play, stop, and describe without the lom_ prefix, though these read as intentional and do not break the overall pattern.

Tool Count4/5

43 tools is well above the typical 3-15 range and would normally signal bloat, but the domain — full control of a DAW — is genuinely broad, spanning session, tracks, clips, notes, automation, devices, mixer, transport, arrangement, library search, audio analysis, and file formats. Each tool has a distinct job and the 7-tool lom_* raw layer earns its place as an escape hatch that keeps the documented surface finite, so the count is high but reasonable.

Completeness4/5

The surface provides full lifecycle coverage for tracks, clips, devices, notes, automation, and transport, with workflow chains explicitly documented (create_track → load_device → create_clip → write_clip_notes → arrange → play). Minor gaps exist — no dedicated save, undo, or live-record tools — but these are reachable one hop away through the documented lom_call/lom_set layer, making them workarounds rather than dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources