Skip to main content
Glama
severity1

terraform-cloud-mcp

by severity1

Related Servers

Alternatives to terraform-cloud-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Terraform CLI operations as tools for Claude and other MCP-compatible AI assistants, enabling AI-driven infrastructure-as-code workflows including planning, applying, and validating Terraform configurations.
      21
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      🌍 Terraform Model Context Protocol (MCP) Tool - An experimental CLI tool that enables AI assistants to manage and operate Terraform environments. Supports reading Terraform configurations, analyzing plans, applying configurations, and managing state with Claude Desktop integration. ⚡️
      371
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that gives Claude (and other MCP-compatible AI tools) full access to your Railway.app infrastructure. Deploy, manage services, check logs, configure environment variables — all through natural conversation.
      30
      9
      -
    • A
      license
      B
      quality
      D
      maintenance
      An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
      8
      30
      187
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your AWS environment. This allows for natural language querying and management of your AWS resources during conversations. Think of better Amazon Q alternative.
      3
      295
      -

    TDQS

    A3.7/5.0

    Scored across 62 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources and actions, with clear boundaries like create/update/get/list for each resource type. However, some overlap exists in variable management between workspace and variable set contexts, and multiple run action tools (cancel, force_cancel, discard) could be confusing without careful reading of descriptions.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, with clear conventions like create_*, get_*, list_*, update_*, assign_*, and unassign_*. All names use snake_case consistently, making the tool set predictable and easy to navigate despite the large count.

    Tool Count2/5

    With 62 tools, this is an extremely large surface that feels heavy and overwhelming for the Terraform Cloud domain. While the API is comprehensive, this many tools will likely cause confusion and selection paralysis for agents, exceeding typical well-scoped MCP servers (3-15 tools).

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for all major Terraform Cloud resources (organizations, workspaces, projects, runs, variables, state versions, etc.). There are no obvious gaps—every resource has create, read, update, and delete/list operations where applicable, plus specialized actions like run management and workspace locking.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive