What is the key difference between MCP Server Terraform and Cloud Tools?

MCP Server Terraform belongs to the Cloud Platforms category with local stdio execution, while Cloud Tools belongs to the Cloud Platforms category with local stdio execution.

How do I install MCP Server Terraform or Cloud Tools in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Server Terraform and Cloud Tools free or paid?

MCP Server Terraform operates under a Free / Open Source model (No auth required). Cloud Tools operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

MCP Server Terraform lists 11 tools with 2 views and 1 GitHub stars. Cloud Tools lists 7 tools with 3 views and 0 GitHub stars.

Can I use both MCP Server Terraform and Cloud Tools together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Server Terraform vs Cloud Tools

In-depth architectural comparison of the MCP Server Terraform and Cloud Tools MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Server Terraform

Cloud Platforms · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Cloud Tools

Cloud Platforms · Local stdio

Quality: 61/100 (Good) | Auth: other

Verdict Summary: Choose MCP Server Terraform if you need specialized Cloud Platforms tools running via a local process. Choose Cloud Tools if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Server Terraform when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: tf_init, tf_validate, tf_plan.

Explore MCP Server Terraform Details

Choose Cloud Tools when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, OVH_APPLICATION_KEY, OVH_CONSUMER_KEY.
Primary tools included: compare_costs, get_commitments, get_costs.

Feature & Specification Comparison

Specification	MCP Server Terraform RajeevSirohi Cloud Platforms	Cloud Tools Cloud Platforms
Summary	Safety-first Terraform operations: plan/apply/destroy with two-step confirmation gates, plan risk & cost analysis that flags expensive always-on resources (NAT gateways, EKS, Azure Firewall), drift detection, import/taint/refresh, provider auth pre-flight checks, and audit logging.	Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.
Category & Scope	Cloud Platforms

Tools & Capabilities Breakdown

MCP Server Terraform Tools (11)

tf_init

Initialize a Terraform working directory

tf_validate

Validate configuration syntax

tf_plan

Run a plan and return the diff + risk/cost summary

tf_apply

Apply changes (requires `confirmed: true`)

tf_destroy

Destroy infrastructure (requires `confirmed: true`)

tf_output

Read output values from state

tf_state

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Server Terraform Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rajeevsirohi-mcp-server-terraform": {
      "command": "npx",
      "args": [
        "-y",
        "@rajsir/mcp-server-terraform"
      ]
    }
  }
}

Cloud Tools Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cloud-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@munhq/cloud-tools"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
        "AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
        "AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
        "GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
        "CLOUDFLARE_ACCOUNT_ID": "YOUR_CLOUDFLARE_ACCOUNT_ID_HERE",
        "OVH_APPLICATION_KEY": "YOUR_OVH_APPLICATION_KEY_HERE",
        "OVH_CONSUMER_KEY": "YOUR_OVH_CONSUMER_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Server Terraform is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Cloud Tools belongs to Cloud Platforms using local stdio subprocess. Select MCP Server Terraform when you need capabilities focused on cloud platforms and Cloud Tools when you require tools for cloud platforms.

More alternatives to MCP Server Terraform More alternatives to Cloud Tools Cloud Platforms category hub Canonical compare URL