Skip to main content
Glama
lilypond-mcp

lilypond-mcp

Related Servers

Alternatives to lilypond-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to generate and edit MuseScore scores from compact text notation and export them as mscz, PDF, PNG, SVG, MIDI, or MP3 without opening the MuseScore GUI.
      11
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables headless and secure control of Inkscape for creating, inspecting, and resizing SVG documents, and exporting to PNG, PDF, and SVG with validation of size, pages, structure, and hashes.
      90
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Drives MuseScore Studio 4.7.6 headlessly to inspect and repair score layout — breaks, measure stretch, styles, element offsets, fitting to N pages, overlap detection, plus PNG/PDF export — while working on versioned copies so the original score is never modified.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to convert music scores between MusicXML, MIDI, ABC, MEI and Humdrum while verifying each result note by note and reporting exactly what was kept or lost. Also supports rendering printable sheet music and audio previews, transposing, extracting parts or bars, validating bars, and comparing versions across formats.
      48 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to create, inspect, edit, render, and export SVG/Inkscape documents through typed drawing tools, with a deterministic offline backend and an optional bridge to a locally running Inkscape instance for limited live editing and snapshots.
      5
      BSD 3-Clause

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: engrave_file operates on a .ly path, engrave_code takes inline source, and lilypond_version reports the engine version. The descriptions explicitly contrast the two engrave tools, reducing any misselection risk.

    Naming Consistency4/5

    engrave_file and engrave_code share a consistent verb_noun pattern, but lilypond_version breaks it with a noun_noun form. The deviation is minor and still readable as a cohesive set.

    Tool Count4/5

    Three tools is a tight, focused scope appropriate for a single-purpose LilyPond engraver wrapper. It's on the lean side but each tool earns its place without redundancy.

    Completeness4/5

    Core workflow (engrave file, engrave inline, check version) is fully covered with no dead ends for typical use. A preview/validate-only or batch operation is absent, but agents can work around this via engrave_code plus engrave_file.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues