Skip to main content
Glama
m053m716

GraphViz MCP

by m053m716
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to GraphViz MCP

No user-submitted related servers found.

    Related Servers

    • diagram-mcp

      JVmano
      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
      15 npm
      MIT

    • Vizdown-MCP

      rutika196
      A
      license
      A
      quality
      D
      maintenance
      Converts Markdown files into professional diagrams such as flowcharts, mind maps, and architecture diagrams using Mermaid.js and custom SVG renderers. It enables users to list, render, and export visualizations in multiple formats including SVG, PNG, and PDF.
      3
      MIT

    • dgv

      ShAInyXYZ
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables planning and maintaining system architecture as typed, linted, live diagrams stored as files in the repo, with MCP tools for cataloging, creating, editing, linting, exporting, and viewing diagrams locally.
      8
      MIT

    • diagrams-mcp

      ByteOverDev
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables generating cloud architecture diagrams, flowcharts, sequence diagrams, and more using three rendering engines: mingrammer/diagrams, Mermaid, and PlantUML.
      3
      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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation2/5

    The set has clear distinct tools like graphviz_environment and graphviz_validate, but graphviz_render and graphviz_render_source are easily confused, and graphviz_publish_markdown and graphviz_sync appear to overlap heavily in purpose. An agent would struggle to reliably pick between these pairs without deeper context.

    Naming Consistency4/5

    Most tools follow a consistent graphviz_<verb> pattern, such as validate, render, and sync. The exception is graphviz_environment, which uses a noun instead of a verb, creating a minor inconsistency.

    Tool Count5/5

    Six tools is a reasonable, focused scope for a GraphViz-specific server. Each tool addresses a core part of the workflow: environment discovery, validation, rendering, source rendering, and Markdown publishing/sync.

    Completeness4/5

    The server covers environment reporting, validation, rendering, and Markdown integration, which appears to be the core domain. The overlap between publish_markdown and sync leaves some ambiguity about the intended lifecycle, but there are no obvious critical gaps for rendering and embedding diagrams.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources