# terraback [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://terraback.io/mcp/  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/terraback

## Description
Scan AWS/Azure/GCP and generate Terraform HCL with import blocks, deterministically, for AI agents.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "terraback": {
    "url": "https://terraback.io/mcp/"
  }
}
```

## Documentation

## What terraback does

The terraback MCP server gives AI agents a way to scan cloud environments in AWS, Azure, and GCP and generate Terraform HCL from the results. The generated configuration includes Terraform import blocks, so the output can describe both infrastructure configuration and the resources that need to be imported.

Its scope is focused on cloud-to-Terraform conversion. The available description does not identify a particular AWS, Azure, or Google Cloud service, resource type, account model, or Terraform provider version. Those details should be confirmed before relying on the server for a specific infrastructure estate.

## How it works

An AI agent sends a request through MCP to scan one of the supported cloud platforms. terraback then produces Terraform HCL and import blocks from the scan. The output is described as deterministic, which makes repeatable generation a central part of the server's behavior.

It also does not describe a deployment workflow. Treat the server as a scanning and code-generation component rather than assuming it provisions infrastructure.

## Tools and capabilities

The stated capabilities are:

- Scanning AWS environments.
- Scanning Azure environments.
- Scanning GCP environments.
- Generating Terraform HCL.
- Adding Terraform import blocks to generated output.
- Producing deterministic results for AI-agent workflows.

The source does not provide formal tool names, parameter schemas, return formats, or examples. An agent integration should therefore obtain those details from the server's current MCP endpoint or documentation before implementation.

## Limitations and notes

No README is available, so installation commands, configuration fields, required environment variables, authentication requirements, transport mode, error behavior, licensing, and client compatibility cannot be confirmed here.

The description confirms support for AWS, Azure, and GCP, but it does not establish feature parity between them. It also does not state whether the generated Terraform covers every discovered resource or only a defined subset. Verify coverage and review generated HCL before using it in an operational Terraform workflow.

_Full upstream README: https://allmcps.com/mcp/terraback/readme_