Skip to main content
Glama
dgmo-mcp
by diagrammo

Related Servers

Alternatives to dgmo-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that generates Mermaid diagrams with live browser preview, supports real-time rendering and SVG/PNG export.
      13
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for generating and editing architecture diagrams from natural language or code, supporting formats like Terraform, docker-compose, Kubernetes, SQL, Mermaid, and PlantUML.
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for creating and editing diagrams using draw.io. Allows generating diagrams from Mermaid or XML, searching shapes, and opening them in draw.io for export.
      2
      0
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct purposes: language lookup (get_language_reference, list_chart_types, get_examples), authoring aids (suggest_chart_type, validate_diagram), output routes (render_diagram, preview_diagram, open_in_app, share_diagram), and cloud storage (put/get/list_space_diagram). The four output-route tools overlap conceptually, but the descriptions clearly delineate SVG/PNG text, browser HTML preview, desktop app, and shareable URL, and check_app_installed explicitly disambiguates open_in_app vs share_diagram. The reference-lookup tools are also carefully cross-referenced (suggest_chart_type appends the reference section, so get_language_reference is only needed on switch), leaving only minor residual ambiguity between render_diagram and preview_diagram.

    Naming Consistency4/5

    All names are snake_case, verb-first, and follow a verb_noun pattern (render_diagram, validate_diagram, share_diagram, list_space_diagrams, get_examples). Minor deviations appear in put_space_diagram and open_in_app, which use a prepositional qualifier rather than a plain noun, but both remain predictable within their sub-groups (cloud CRUD uses put/get/list).

    Tool Count5/5

    Fourteen tools is well within a healthy range and each one earns its place: authoring helpers, output routes, cloud CRUD, and reporting cover the domain without redundancy. The grouping into language/reference, render/output, and cloud storage is coherent and not padded.

    Completeness4/5

    The surface covers the full lifecycle of authoring (suggest, reference, examples, validate, render), delivery (preview, share, open, report), and cloud storage with put/get/list. The main gap is that the cloud space is read-write-list only — there is no delete or move/rename operation for space diagrams, and no folder-listing tool, which an agent managing a space would likely need.

    Maintenance

    ActivityActive
    ResponsivenessLimited data