A
licenseC
qualityA
maintenanceEnables 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
lilypond-mcp
by wspringer
Related Servers
Alternatives to lilypond-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables driving Inkscape headlessly from an MCP client, with verified SVG editing, rendering, optimization, and animation tools.23MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.5BSD 3-Clause
- FlicenseNot gradedqualityAmaintenanceEnables AI models to convert LaTeX snippets to Typst, validate Typst syntax, retrieve documentation chapters, and render Typst code as PNG images.-
- AlicenseNot gradedqualityBmaintenanceTurns 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
- AlicenseAqualityDmaintenanceConverts diagrams (Mermaid, PlantUML, Graphviz, etc.) to SVG, PNG, PDF, or JPEG images using Kroki.io. Supports generating diagram URLs and downloading diagrams to local files.28 npm8MIT
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
ActivitySlowing
ResponsivenessResponsive