Skip to main content
Glama
TravisLinkey

Provision Stack MCP

by TravisLinkey

Related Servers

Alternatives to Provision Stack MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to provision and manage cloud infrastructure and AI/ML workloads—such as GPUs, nodes, storage, networking, databases, Kubernetes, and training/inference resources—through natural language. It also provides a universal REST tool for authenticated access to the underlying cloud API.
      46
      31 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      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
    • 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
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with natural language control over AWS, Azure, GCP, and Alibaba Cloud infrastructure through dynamic API discovery and execution. Supports 51,900+ cloud operations and includes OpenTofu integration for complete infrastructure lifecycle management.
      3
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT

    TDQS

    A4.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Suggestions.generate for options, providers.detect for provider discovery, pricing.get for component costs, credentials.list for credential checks, region.detect for region resolution, and deploy.* tools cover the full lifecycle with clear differentiation (e.g., deploy.destroy vs deploy.teardown_latest). Billing tools are separate. No overlap.

    Naming Consistency5/5

    All tools follow a consistent category.action pattern (noun.verb) using snake_case in the verb part (e.g., suggestions.generate, deploy.teardown_latest, billing.top_up). The pattern is uniform across the set, making it predictable for agents.

    Tool Count5/5

    With 12 tools, the surface is well-scoped. It covers discovery (detect, list), pricing (get, generate), deployment (run, status, destroy, list, teardown_latest), and billing (balance, top_up). No tool is extraneous, and the count feels appropriate for a provisioning domain.

    Completeness5/5

    The tool set appears complete for the domain of provisioning cloud stacks. It covers the full workflow: initial discovery, pricing, deployment, monitoring, teardown, and billing. No obvious gaps like missing deployment modification or log retrieval, given the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues