Skip to main content
Glama
xmpuspus

cloudwright-mcp

by xmpuspus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to cloudwright-mcp

No user-submitted related servers found.

    Related Servers

    • Provision Stack MCP

      TravisLinkey
      A
      license
      A
      quality
      B
      maintenance
      Cloud infrastructure provisioning via natural language. Enables deploying production-ready infrastructure on AWS, GCP, Azure, or Oracle with a single prompt.
      12
      9 npm
      MIT

    • insideout-mcp

      luthersystems
      A
      license
      A
      quality
      C
      maintenance
      AI infrastructure design agent. Describe your app in plain English; Riley designs, prices, and deploys AWS or GCP infrastructure with generated Terraform.
      24
      Apache 2.0

    • CloudOps OS MCP

      saihardhikreddy
      A
      license
      Not graded
      quality
      B
      maintenance
      Autonomous multi-agent pipeline that analyzes Terraform files for cost, governance, and compliance issues, providing real-time remediation and XAI console for human-in-the-loop approval.
      MIT
    • Synlake MCP Server by Synlake-ai

      Synlake MCP Serverofficial

      Synlake-ai
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover, evaluate, and provision cloud infrastructure across AWS, GCP, and Azure with cross-cloud normalization, cost comparisons, and deployable execution kits.
      5
      8 npm
      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

    A4.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear 'when to use' cross-references, but there is slight overlap between security_scan and lint_architecture (both catch similar issues), and between scan_terraform and security_scan (both scan for security misconfigurations). The descriptions help distinguish them, so confusion is unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: design_architecture, modify_architecture, compare_providers, estimate_cost, scan_terraform, chat_create_session, etc. The 'chat_' prefix for session tools clearly groups them, and each verb is meaningful and non-redundant.

    Tool Count5/5

    19 tools is slightly above the typical 3-15 range but well-justified given the server's broad scope: architecture design, cost estimation, compliance, security, IaC export, session management, and catalog lookup. Each tool has a clear role, and the count is reasonable for the domain.

    Completeness5/5

    The tool surface covers the full architecture lifecycle: design, modify, compare, cost, validate, security, lint, blast radius, diff, export, and session management. Missing deployment/apply is intentional (server does not deploy), and the catalog lookup tools support hand-authoring. No obvious gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources