Skip to main content
Glama
fernando-moretes

Moretes AWS Architect MCP

by fernando-moretes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Moretes AWS Architect MCP

No user-submitted related servers found.

    Related Servers

    • AWS Well-Architected Framework

      artofthepossible
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      This 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.
      -

    • Pattern Intelligence MCP

      mateusdcc
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      4 npm
      3
      MIT

    • terraform-mcp

      imashish-in
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • Cloud Operations Runbook

      skmahe1077
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables cloud and platform engineers to investigate AWS incidents by grounding responses in approved runbooks and operational evidence, with authenticated access, citations, observability, and human approval before any write action.
      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 48 tools

    Disambiguation3/5

    Most tools target a distinct artifact type (each *_review takes a different input: Terraform plan, CloudFormation, OpenAPI, k8s, IAM), but several families overlap: architecture_pattern's provider mapping duplicates service_equivalents, service_compare vs service_equivalents is a fine line, and aws_regions vs aws_regional_availability are easy to misselect. The dense, caveat-heavy descriptions do help an agent recover, so it is workable rather than clean.

    Naming Consistency3/5

    Everything is snake_case and readable, but the convention mixes noun_verb (dependency_manifest_review, requirements_check, iam_policy_review) with verb_noun (service_compare, code_review_architecture) and bare noun phrases (architect_panel, aws_regions, architecture_pattern, c4_model). No single predictable pattern lets an agent guess a name without reading the list.

    Tool Count2/5

    48 tools is far past a comfortable surface for one server, and the catalogue carries real context cost before any work begins. Each tool is individually defensible given the breadth (reviews, calculators, diagram builders, AWS knowledge lookups), but bundling them into one endpoint makes selection expensive.

    Completeness4/5

    The advisory lifecycle is broadly covered: requirements, pattern selection, ADRs, C4/sequence diagrams, cost/latency/capacity math, IaC and config reviews, incident postmortem and runbook, plus live AWS documentation lookups. Gaps are mostly deliberate (no execution, no live pricing) but real: no network/VPC topology design and no service-quota or multi-account/landing-zone modeling.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources