Skip to main content
Glama
RedHold

diagrams-so

Official
by RedHold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to diagrams-so

No user-submitted related servers found.

    Related Servers

    • 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

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

    • archdiagram

      bharathgnana
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for generating architecture diagrams with official vendor icons from natural language descriptions. Provides tools to validate specs, render diagrams, search icon catalog, and list available services.
      3
      MIT

    • Azure Diagram MCP Server

      Jah-yee
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that generates professional infrastructure diagrams using the Python diagrams DSL, with first-class Azure support and GitHub Copilot integration for natural language diagram generation.
      4
      MIT

    • fcp-drawio

      os-tack
      A
      license
      B
      quality
      B
      maintenance
      MCP server that enables LLMs to create and edit draw.io diagrams using high-level intent commands, with automatic layout and styling.
      4
      6 npm
      4
      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

    A3.9/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct object/action: diagram CRUD vs versioning vs warnings vs relayout vs gallery vs usage/prompt helpers. Although update_diagram and edit_diagram are near-synonyms, their descriptions distinguish direct metadata/XML changes from AI natural-language edits, so an agent should not confuse them.

    Naming Consistency4/5

    Almost all names are snake_case verb_noun pairs (list_diagrams, get_version, fork_template, list_capabilities), with whoami as the only notable deviation from the object-bearing pattern. This is a minor exception to an otherwise consistent convention.

    Tool Count3/5

    At 23 tools this sits in the 16-25 range that feels heavy; the API covers many subdomains (diagram lifecycle, AI generation, warnings, relayout, gallery, usage) but several helper tools (whoami, get_usage, get_usage_history, clarify_prompt, enhance_prompt) could arguably be consolidated. Still, most tools map to a distinct operation.

    Completeness5/5

    The set covers the full diagram lifecycle: create (generate/import/fork), read (get/list), update (update/edit), delete, revert, version history, export, and warnings. There are no obvious dead ends; prompt helpers and usage tracking round out the workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources