Skip to main content
Glama
RajeevSirohi

mcp-server-terraform

by RajeevSirohi

Related Servers

Alternatives to mcp-server-terraform

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server that integrates Claude with the Terraform Cloud API, allowing Claude to manage your Terraform infrastructure through natural conversation.
    62
    23
    MIT
  • 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.
    13 npm
    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
    11 npm
    -
  • 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
    4 npm
    188
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables managing Terrakube infrastructure through natural language, handling workspace management, variables, modules, and organization operations.
    16
    6 npm
    3
    Apache 2.0

TDQS

A4.2/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a distinct purpose: tf_apply applies changes, tf_destroy destroys, tf_drift detects drift, tf_init initializes, tf_output reads outputs, tf_plan plans, tf_preflight checks auth, tf_resource handles resource-level state ops, tf_state manages state, tf_validate validates config, tf_workspace manages workspaces. No overlap.

Naming Consistency5/5

All tools follow the tf_ prefix with clear verb names (e.g., apply, destroy, drift, init, output, plan, preflight, resource, state, validate, workspace). The pattern is consistent and predictable.

Tool Count5/5

11 tools cover the essential Terraform operations comprehensively—init, validate, plan, apply, destroy, state management, resource ops, drift detection, outputs, workspace management, and preflight checks. The count is well-scoped for the domain.

Completeness5/5

The tool set covers the full Terraform workflow: init, validate, plan, apply, destroy, plus state manipulation, resource import/taint/untaint/refresh, drift detection, output reading, workspace management, and preflight authentication checks. No obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues