Log inSubmit server
T

Terraback

Scans AWS, Azure, and GCP and produces deterministic Terraform HCL with import blocks for AI agents.

InstallWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Terraback

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://terraback.io/mcp/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The terraback MCP server scans AWS, Azure, and GCP for AI agents. It generates Terraform HCL that includes import blocks, with deterministic output. Reach for it when an agent needs to turn cloud environments into Terraform configuration across these providers.

Use cases

  • Scan AWS resources for Terraform generation
  • Scan Azure environments for importable infrastructure code
  • Scan GCP environments for deterministic HCL output
  • Generate Terraform import blocks for an AI agent

Key features

  • AWS scanning
  • Azure scanning
  • GCP scanning
  • Terraform HCL generation
  • Import block generation
  • Deterministic output

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 4d ago

Recent health check succeeded.

How Terraback works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Terraback

terraback is an MCP server that connects AI agents to AWS, Azure, and GCP for cloud scanning and deterministic Terraform HCL generation. Its main capabilities include producing Terraform configuration with import blocks from scan results, giving agents a way to represent discovered cloud infrastructure as code.

The source identifies the service and its cloud-scanning and Terraform-generation capabilities, but gives no package command, transport configuration, or client setup instructions.

No MCP client names or client-specific setup requirements are listed, so verify support with the current terraback documentation before configuring it in Cursor.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTerraback AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/terraback?style=directory)](https://allmcps.com/mcp/terraback)
HTML Embed
<a href="https://allmcps.com/mcp/terraback"><img src="https://allmcps.com/api/badge/terraback?style=directory" alt="Terraback on AllMCPs" /></a>