A
licenseNot graded
qualityD
maintenanceScans AWS environments and generates professional architecture diagrams showing VPC networking, compute, storage, and security resources.
MIT
arch-diagram-mcp
by apatilgtn
Related Servers
Alternatives to arch-diagram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables visualization of Terraform plan changes as interactive cloud architecture diagrams with official AWS, Azure, and GCP icons, showing resource dependencies and changes.7MIT
- AlicenseAqualityAmaintenanceLets AI agents draw professional cloud architecture diagrams with the official AWS, Azure and Google Cloud icons, from a plain description, a JSON graph or Terraform code.71,664AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceProfessional AI-powered architecture diagram generator with multi-cloud support and MCP server integration. Generates beautiful, accurate diagrams with provider-specific icons for AWS, Azure, GCP, Kubernetes, and more.11MIT
- AlicenseAqualityAmaintenanceGenerates editable .drawio architecture diagrams from descriptions or reference images, with secure asset resolution, validation, and revision-based approvals.1133 npm1MIT
- AlicenseAqualityDmaintenanceGenerates professional architecture diagrams from natural language descriptions using template-driven prompts and swappable AI image providers.72MIT
TDQS
A3.7/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have clearly distinct purposes: rendering (generate_architecture_diagram), discovery (search_icons, list_icon_categories, list_templates, get_template), validation (validate_diagram vs review_architecture), and import (diagram_from_terraform vs diagram_from_inventory). Minor overlap between search_icons and list_icon_categories (both surface icons) and between validate_diagram and review_architecture (both inspect a spec), but descriptions clarify the intent difference.
Naming Consistency4/5
Most tools follow a verb_noun pattern (search_icons, list_templates, get_template, validate_diagram, review_architecture) and the two import tools consistently use diagram_from_<source>. Deviations exist: server_info is noun-only and generate_architecture_diagram is a longer verb phrase, but the set reads predictably overall.
Tool Count5/5
Ten tools is well-scoped for a diagram generation server, covering rendering, discovery, templates, validation, review, and two import sources without redundancy. Each tool earns its place in the workflow.
Completeness4/5
The surface covers the full diagram lifecycle: discover icons, load templates, generate, validate, review, and import from Terraform/inventory. Minor gaps remain—no explicit tool to save/manage custom templates or to retrieve/edit previously generated diagram files—but core workflows are well supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues