What is the key difference between Cloudwright and Terraform MCP Server?

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

How do I install Cloudwright or Terraform MCP Server 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 Cloudwright and Terraform MCP Server free or paid?

Cloudwright operates under a BYOK (Pay Provider Direct) model (API Key required). Terraform MCP Server operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Cloudwright lists 6 tools with 3 views and 32 GitHub stars. Terraform MCP Server lists 5 tools with 2 views and 1,531 GitHub stars.

Can I use both Cloudwright and Terraform MCP Server 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

Cloudwright vs Terraform MCP Server

In-depth architectural comparison of the Cloudwright and Terraform MCP Server 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

Cloudwright

Cloud Platforms · Local stdio

Quality: 47/100 (Fair) | Auth: API Key required

Terraform MCP Server

Cloud Platforms · Local stdio

Quality: 74/100 (Great) | Auth: API Key required

Verdict Summary: Choose Cloudwright if you need specialized Cloud Platforms tools running via a local process. Choose Terraform MCP Server 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 Cloudwright when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: ANTHROPIC_API_KEY, OPENAI_API_KEY.
Primary tools included: Natural-language architecture design, Cost estimation with confidence flags, Framework-mapped compliance checks.

Explore Cloudwright Details

Choose Terraform MCP Server when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TFE_ADDRESS, TFE_TOKEN, TF_MCP_SHARED_SECRET, TFE_SKIP_TLS_VERIFY, LOG_LEVEL, LOG_FORMAT, TRANSPORT_MODE, TRANSPORT_HOST.

Feature & Specification Comparison

Specification	Cloudwright xmpuspus Cloud Platforms	Terraform MCP Server hashicorp VerifiedCloud Platforms
Summary	Natural-language cloud architecture intelligence for AWS, GCP, Azure, and Databricks. 19 tools for architecture design, cost estimation, compliance validation (HIPAA, SOC 2, FedRAMP, GDPR, PCI-DSS, Well-Architected), security scanning, Terraform/CloudFormation export, and blast-radius analysis.	The official Terraform MCP Server seamlessly integrates with the Terraform ecosystem, enabling provider discovery, module analysis, and direct Registry API integration for advanced Infrastructure as Code workflows.

Tools & Capabilities Breakdown

Cloudwright Tools (6)

Natural-language architecture design

Cost estimation with confidence flags

Framework-mapped compliance checks

Terraform, OpenTofu, Pulumi, and CloudFormation export

Migration planning with evidence gates

Offline review, security, and policy checks

Terraform MCP Server Tools (5)

Supports stdio and streamable HTTP transports

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).

Cloudwright Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "xmpuspus-cloudwright": {
      "command": "npx",
      "args": [
        "-y",
        "xmpuspus-cloudwright"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      }
    }
  }
}

Terraform MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hashicorp-terraform-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "hashicorp-terraform-mcp-server"
      ],
      "env": {
        "TFE_ADDRESS": "YOUR_TFE_ADDRESS_HERE",
        "TFE_TOKEN": "YOUR_TFE_TOKEN_HERE",
        "TF_MCP_SHARED_SECRET": "YOUR_TF_MCP_SHARED_SECRET_HERE",
        "TFE_SKIP_TLS_VERIFY": "YOUR_TFE_SKIP_TLS_VERIFY_HERE",
        "LOG_LEVEL": "YOUR_LOG_LEVEL_HERE",
        "LOG_FORMAT": "YOUR_LOG_FORMAT_HERE",
        "TRANSPORT_MODE": "YOUR_TRANSPORT_MODE_HERE",
        "TRANSPORT_HOST": "YOUR_TRANSPORT_HOST_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

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