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
      F
      license
      A
      quality
      C
      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
      -

    • 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.
      2,955 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 11 tools

    Disambiguation4/5

    Most tools have distinct purposes, but preview_diagram and generate_report both render multiple diagrams and open a browser, creating potential overlap. render_diagram, open_in_app, and share_diagram are clearly differentiated by output medium and use case. The reference/information tools (get_language_reference, list_chart_types, get_examples, suggest_chart_type) are distinct enough in their guidance.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: check_app_installed, get_language_reference, preview_diagram, share_diagram, list_chart_types, open_in_app, render_diagram, get_examples, validate_diagram, generate_report, suggest_chart_type. The minor variation in open_in_app (verb_preposition_noun) does not break predictability.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a diagramming server. Each tool serves a clear role: discovery, validation, rendering, previewing, sharing, app integration, and reporting. No extraneous or missing tools inflate or thin the surface.

    Completeness4/5

    The tool surface covers the core diagram lifecycle: type suggestion, reference/examples, validation, rendering, previewing, sharing, and in-app editing. A minor gap is the absence of an explicit file-writing or save-diagram tool, though open_in_app and render_diagram partially address this. Overall, the coverage is strong for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources