What is the key difference between Tfmcp and Cloudwright?

Tfmcp belongs to the Cloud Platforms category with local stdio execution, while Cloudwright belongs to the Cloud Platforms category with local stdio execution.

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

Tfmcp operates under a Free / Open Source model (No auth required). Cloudwright operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Tfmcp lists 6 tools with 1 views and 371 GitHub stars. Cloudwright lists 6 tools with 1 views and 32 GitHub stars.

Can I use both Tfmcp and Cloudwright 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.

How do I install Tfmcp or Cloudwright in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Tfmcp and Cloudwright free to use, or do they require API keys?

Tfmcp is listed under a Free / Open Source model with No auth required . Cloudwright operates under a BYOK (Pay Provider Direct) model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Tfmcp and Cloudwright at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both nwiizo-tfmcp and xmpuspus-cloudwright as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Tfmcp has a Quality Score of 47 /100 ( Fair ) with 1 views, 0 installs, and 371 GitHub stars. Cloudwright holds a Quality Score of 49 /100 ( Fair ) with 1 views, 0 installs, and 32 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Tfmcp vs Cloudwright

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

Tfmcp

Cloud Platforms · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

Cloudwright

Cloud Platforms · Local stdio

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

Verdict Summary: Choose Tfmcp if you need specialized Cloud Platforms tools running via a local process. Choose Cloudwright 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 Tfmcp 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).
You have access to required keys: TERRAFORM_DIR, TFMCP_LOG_LEVEL, HOME, PATH.
Primary tools included: Validate, format, plan, apply, and destroy workflows, Analyze Terraform plans with risk scoring and recommendations, Support for local Terraform CLI and Terraform Cloud/Enterprise APIs.

Explore Tfmcp Details

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.

Feature & Specification Comparison

Specification	Tfmcp nwiizo Cloud Platforms	Cloudwright xmpuspus Cloud Platforms
Summary	A Terraform MCP server allowing AI assistants to manage and operate Terraform environments, enabling reading configurations, analyzing plans, applying configurations, and managing Terraform state.	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.
Category & Scope

Tools & Capabilities Breakdown

Tfmcp Tools (6)

Validate, format, plan, apply, and destroy workflows

Analyze Terraform plans with risk scoring and recommendations

Support for local Terraform CLI and Terraform Cloud/Enterprise APIs

Repository intelligence including project detection and quality checks

MCP deployment via stdio and streamable HTTP with security features

Docker and native Rust installation options

Cloudwright Tools (6)

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

Tfmcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "nwiizo-tfmcp": {
      "command": "npx",
      "args": [
        "-y",
        "nwiizo-tfmcp"
      ],
      "env": {
        "TERRAFORM_DIR": "YOUR_TERRAFORM_DIR_HERE",
        "TFMCP_LOG_LEVEL": "YOUR_TFMCP_LOG_LEVEL_HERE",
        "HOME": "YOUR_HOME_HERE",
        "PATH": "YOUR_PATH_HERE"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Tfmcp More alternatives to Cloudwright Cloud Platforms category hub