Moretes AWS Architect MCP
Related Servers
Alternatives to Moretes AWS Architect MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AWS infrastructure-as-code guidance through Terraform Registry documentation and module lookups, local Terraform plan policy scans for public S3, unencrypted storage, wildcard IAM, and open security groups, plus plain-language explanations of common AWS resource types.79 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides cloud architecture analysis, recommendations, and artifacts (diagrams, ADRs, deployment comparisons) for any project, supporting AWS, GCP, and Azure.1-
- -licenseNot gradedqualityNot gradedmaintenanceThis server provides guidance and recommendations based on AWS's Well-Architected Framework for cloud architectures, enabling analysis and review focused on operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.-
- AlicenseNot gradedqualityCmaintenanceEnables planning AWS architectures, reviewing plans, and provisioning resources after administrative approval with durable execution tracking.2Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to make evidence-aware design-pattern decisions by analyzing cases, comparing options, detecting misuse, stress-testing assumptions, planning adoption, writing ADRs, and generating evidence plans with transparent scoring.83MIT
- AlicenseNot gradedqualityCmaintenanceEnables state-aware Terraform/OpenTofu plan evaluation against live AWS topology and CloudWatch telemetry, detecting reliability blast radius and FinOps waste before merge.Apache 2.0
TDQS
Scored across 48 tools
Most tools have a sharply distinct target artifact or computation (cost_model vs capacity_plan vs latency_budget vs queue_sizing are clearly separated), and the review tools each bind to a specific input format (CloudFormation, Terraform plan, OpenAPI, Kubernetes, MCP config). A few pairs invite confusion: aws_regions vs aws_regional_availability, service_compare vs service_equivalents vs architecture_pattern's provider mapping, and integration_catalog vs integration_config vs mcp_config_review.
Names are uniformly lower_snake_case and mostly follow a domain-noun-first pattern with an optional action suffix (iam_policy_review, cost_model, slo_budget, queue_sizing). Minor deviations exist where the verb lands mid-name (code_review_architecture, aws_knowledge_search) and some names are bare nouns while siblings are noun_verb, but nothing is ambiguous or camelCase-mixed.
48 tools is heavy even for a broad architecture-advisory domain; the surface spans cost, reliability, security, AI-agent design, IaC review and AWS docs lookup in one flat list. Without grouping or prefixes, an agent must scan a large set to find the right tool, and several near-neighbors increase selection cost.
Coverage is unusually thorough: discovery/requirements, pattern selection, ADR, Well-Architected review, capacity/cost/SLO/latency/queue math, DR, migration, diagrams (C4/sequence/Mermaid), data classification, AI-agent planning, and artifact reviews across IaC, IAM, OpenAPI, MCP config and dependencies. Gaps are minor and largely deliberate (no execution/deployment, no network/VPC topology or multi-account landing-zone design, no backup-plan generator).