Skip to main content
Glama
Dorico Maestro

Dorico Maestro

Related Servers

Alternatives to Dorico Maestro

  • A
    license
    A
    quality
    B
    maintenance
    An AI music production and mixing partner for Ableton Live via MCP. Program expressive MIDI clips, design synth parameters, shape automation curves, arrange on the timeline, and mix tracks with real-time verified feedback.
    63
    1
    AGPL 3.0

Related Servers

  • A
    license
    C
    quality
    B
    maintenance
    A Model Context Protocol server that provides programmatic control over MuseScore through a WebSocket-based plugin system, allowing AI assistants to compose music, add lyrics, navigate scores, and control MuseScore directly.
    65
    150
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables an AI assistant to control a live MuseScore Studio 4.6.x score over MCP, adding and reading notes, rests, tuplets and lyrics alongside a notation layer of slurs, dynamics, articulations, hairpins, ties, clefs, key signatures and tempo marks. It also offers a compact passage format that reads and writes whole sections of music with validation and verification, making large scores far cheaper to inspect and edit.
    MIT

TDQS

A3.9/5.0

Scored across 40 tools

Disambiguation4/5

Most tools target a clearly distinct action (connect, get_status, read_selection, transpose, save, export_pdf, analyze_harmony) and the descriptions actively cross-reference alternatives, which is unusually strong disambiguation. However, render_to_dorico is explicitly described as 'the lower half of write_score', add_notes/add_rest/write_score overlap on note entry, and set_time_signature/set_key_signature are deliberate no-op stubs that duplicate advice given by open_popover and write_score. The read family (get_status, read_selection, read_score, read_open_score, read_project_info) is large but well-differentiated by scope.

Naming Consistency3/5

Naming is uniformly snake_case and readable, and many tools follow verb_noun (get_status, read_selection, write_score, add_notes, export_pdf, import_musicxml, check_voice_leading). But there are many bare nouns and single words (transpose, save, playback, navigate, project_file, playback_state, playback_setup, plugin_state, score_schema, instrument_range) mixed in, so the verb_noun pattern is not predictable across the set.

Tool Count2/5

40 tools is well past the point where an agent can hold the surface in view, spanning Dorico control, offline music theory, VST/playback configuration, MusicXML conversion and a command-catalog escape hatch. Each tool is individually justified, but several are narrow conveniences (rename_player, activate_playback, plugin_state, set_time_signature stubs) that inflate the set. The scope is genuinely broad, yet the count is heavy enough to slow tool selection.

Completeness4/5

Coverage is broad and lifecycle-complete for the main workflows: connect, status/selection reads, note entry, score writing, export/import, save/project file, flows, playback and setup, plus offline analysis and a catalog escape hatch for anything missing. Real gaps exist (pitch and caret position unavailable via the API, key/time signatures not settable directly, no player deletion), but each is documented with a concrete workaround rather than left as a dead end.

Maintenance

ActivityNo data
ResponsivenessOutdated data