Skip to main content
Glama
diagrammo

dgmo-mcp

Official
by diagrammo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to dgmo-mcp

No user-submitted related servers found.

    Related Servers

    • mermaid-live-mcp

      iishyfishyy
      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
      -

    • draft1-mcp

      abdelhadi-azouni
      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

    • drawio

      achmadya-dev
      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

    • excalidraw-mcp

      thiendt1608
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for creating and managing Excalidraw diagrams, supporting elements, libraries, icons, import/export, and auto-layout flowcharts.
      3,837 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.1/5.0

    Scored across 14 tools

    Disambiguation4/5

    The set cleanly separates authoring aids (suggest_chart_type, get_language_reference, get_examples, validate_diagram) from output routes (render_diagram, preview_diagram, share_diagram, open_in_app) and cloud storage operations. The main risk is among the output routes—render_diagram vs preview_diagram and share_diagram vs open_in_app could momentarily confuse, but descriptions make the destination and return type clear. check_app_installed further disambiguates routing decisions.

    Naming Consistency4/5

    All tools use snake_case with a verb_noun pattern, and the cloud tools consistently scope with the space_ prefix (put/get/list_space_diagram). Minor deviations like open_in_app and check_app_installed break the strict verb_noun_ pattern but remain readable and intentional. Overall predictable.

    Tool Count5/5

    14 tools fit comfortably in the well-scoped range and each covers a distinct facet of the diagram workflow (chartering, reference, validation, rendering, output, cloud persistence). No tool feels redundant or padded.

    Completeness4/5

    The surface covers the full authoring lifecycle from chart suggestion through validation, rendering, sharing, and report generation, plus cloud read/write/list. The one notable gap is a delete_space_diagram operation—cloud storage supports create/read/list but no removal. Agents can otherwise complete all core workflows.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources