Log inSubmit server

Terraform MCP Server vs Wraps

A side-by-side look at the Terraform MCP Server and Wraps MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Terraform MCP Server logoTerraform MCP ServerCloud Platforms · Remote HTTP/SSEThe 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.79GreatAuth: api key requiredWraps logoWrapsCloud Platforms · Local subprocess (stdio)Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.49FairAuth: not declared

Verdict: choose Terraform MCP Server for cloud platforms work over a hosted endpoint; choose Wraps for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Terraform MCP Server logoChoose Terraform MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
Explore Terraform MCP Server

Wraps logoChoose Wraps when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
Explore Wraps

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTerraform MCP Server logoTerraform MCP ServerWraps logoWraps
CategoryCloud PlatformsCloud Platforms
Quality signal79/100 · Great49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars1,55264
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Terraform MCP Server View Wraps

Tools & capabilities

Terraform MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Wraps tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Terraform MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hashicorp-terraform-mcp-server": {
      "url": "https://kiro.dev/docs/mcp/"
    }
  }
}

Wraps

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wraps": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/cli"
      ]
    }
  }
}

Frequently asked questions

Terraform MCP Server is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Wraps belongs to Cloud Platforms and uses a local stdio subprocess. Pick Terraform MCP Server for cloud platforms work and Wraps for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Terraform MCP Server is listed as free. Auth: api key required. Wraps has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add hashicorp-terraform-mcp-server and wraps as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Terraform MCP Server has a quality signal of 79/100 (Great) with 3 views, 0 installs and 1,552 GitHub stars. Wraps has 49/100 (Fair) with 1 views, 0 installs and 64 GitHub stars.

Popular comparisons with Terraform MCP Server

Popular comparisons with Wraps