Skip to main content
Glama

Related Servers

Alternatives to drawspec

  • 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
    8 npm
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    Enables agents to turn short specs, Mermaid, or CSV data into laid-out SVG diagrams and charts, and to validate and audit the result for overlapping labels, arrows through boxes, and spilling text before showing it to anyone. Exposes render, describe, validate, audit, export, and infer tools so drawings can be generated, checked, and converted to formats like PNG, PDF, draw.io, and Excalidraw.
    6
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    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
  • F
    license
    B
    quality
    B
    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
    -
  • A
    license
    A
    quality
    B
    maintenance
    MCP server that turns AI into an SVG artist. One rendering engine with a rich JSON schema, AI controls all design parameters. Renders animated SVGs with CSS @keyframes and SMIL animations. Supports 16+ element types, parametric curves, pattern groups, gradient/filter/clip/mask definitions, and PNG preview. No external dependencies, runs locally via npx.
    3
    199 npm
    28
    MIT

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation4/5

validate and render are mostly distinct (one checks, one draws), but both return located violations, so an agent could plausibly reach for render while drafting and lose the stated benefit of validate. kinds is clearly separate as the vocabulary lookup. The boundary is workable but not perfectly crisp.

Naming Consistency4/5

All three names are single lowercase tokens with no style mixing (no camelCase/snake_case clash), which is predictable. However, the set mixes parts of speech—two imperative verbs (validate, render) and one bare noun (kinds)—so it is not a true verb_noun convention.

Tool Count4/5

Three tools is on the lean side but each earns its place: validate for pre-flight checks, render for output, kinds for discovery. For a focused document-to-SVG service this is well-scoped rather than padded or thin.

Completeness4/5

The core lifecycle—learn the vocabulary (kinds), check the document (validate), produce output (render)—is fully covered, and documents live outside the server so CRUD is unnecessary. Minor gaps remain, such as no way to introspect the full document schema beyond the kind vocabulary or to fetch worked examples.

Maintenance

ActivityActive
ResponsivenessResponsive