Cloudwright vs Tfmcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cloudwright vs Tfmcp
In-depth architectural comparison of the Cloudwright and Tfmcp 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
Tfmcp
Cloud Platforms · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Cloudwright if you need specialized Cloud Platforms tools running via a local process. Choose Tfmcp 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: Typed YAML architecture specs with version control friendliness, Cost estimation with confidence flags per line item, Compliance reports mapped to specific control IDs.
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.
A Terraform MCP server allowing AI assistants to manage and operate Terraform environments, enabling reading configurations, analyzing plans, applying configurations, and managing Terraform state.
Category & Scope
Tools & Capabilities Breakdown
Cloudwright Tools (6)
Typed YAML architecture specs with version control friendliness
Cost estimation with confidence flags per line item
Compliance reports mapped to specific control IDs
Infrastructure code export for Terraform, OpenTofu, Pulumi, and CloudFormation
ASCII, Mermaid, D2, and editable web canvas diagrams
MCP server integration for use with multiple AI coding agents
Tfmcp Tools (80)
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 is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Tfmcp belongs to Cloud Platforms using local stdio subprocess. Select Cloudwright when you need capabilities focused on cloud platforms and Tfmcp when you require tools for cloud platforms.