Skip to main content
Glama
wspringer

lilypond-mcp

by wspringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lilypond-mcp

No user-submitted related servers found.

    Related Servers

    • inkscape-mcp

      Berrio
      A
      license
      B
      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.
      19
      MIT

    • Infographic Agent Kit

      steve-8000
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns structured JSON content into resolved, audited infographic plans and renders them as SVG or executable Figma Plugin API scripts, exposing theme packs, grammars, planning, auditing and export tools over stdio. Also lets hosts inspect theme provenance and layout decisions so different tools produce identical frames.
      MIT

    • GraphViz MCP

      m053m716
      F
      license
      B
      quality
      C
      maintenance
      Enables creating and maintaining technical diagrams from .dot sources, with validation, rendering to SVG/PNG/PDF, and publishing into Markdown while automatically partitioning oversized graphs.
      6
      -

    • diagram-mcp

      JVmano
      A
      license
      A
      quality
      C
      maintenance
      Renders diagram-as-code to PNG files on your disk, and also provides text-art previews and syntax validation, all locally without a browser or network.
      4
      4 npm
      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.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

    ActivityMaintained
    ResponsivenessResponsive

    Resources