# TerraVision [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/patrickchugh/terravision  
**GitHub Stars:** 1660  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/terravision

## Description
Cloud architecture diagrams generated from terraform plan, with official AWS, Azure, GCP icons

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "terravision": {
    "command": "uvx",
    "args": ["--from","terravision[mcp]","terravision"]
  }
}
```

## Documentation

## What the TerraVision MCP server does

The TerraVision MCP server creates cloud architecture diagrams for AWS, Azure, and Google Cloud. It can start with a plain-language description supplied through an AI assistant, or it can inspect Terraform code and draw the infrastructure that code describes. The diagrams use official-style provider icons and show resources within structures such as VPCs, subnets, zones, and resource groups.

The project also supports the reverse direction: describe a design, receive a diagram, and have Terraform produced from that design. This makes it suitable for early architecture work as well as visualizing existing infrastructure definitions.

## How it works

An MCP-compatible assistant invokes TerraVision while the user requests a diagram or provides Terraform-related input. Graphviz performs the drawing locally. The resulting diagram can appear in the assistant interface when using supported desktop integrations. With Claude Code, diagrams are saved in a `diagrams` directory within the project.

The same project can be used with multiple cloud providers. Examples in the repository cover AWS, Azure, and Google Cloud designs, including three-tier applications, Kubernetes environments, hub-and-spoke networks, data pipelines, serverless systems, and multi-region or multi-account layouts. These examples document supported diagram scenarios, but they do not establish that every cloud service or Terraform resource is supported.

## Setup and configuration

The TerraVision MCP server requires Graphviz and Git. The installation instructions also use `uv` for Claude Code, Codex CLI, Antigravity CLI, and other MCP clients; Claude Desktop supplies its own runtime on Windows and macOS. Terraform is optional and is needed when drawing diagrams from Terraform code.

Claude Desktop users can install the `.mcpb` package from the latest GitHub release. Claude Code users install the project through its plugin marketplace, while ChatGPT desktop users add the GitHub marketplace and select the TerraVision plugin. Codex CLI has corresponding marketplace and plugin commands. On Linux, Claude Desktop requires `uv` to be installed separately.

After installing prerequisites, restart the relevant application or terminal so it can find the installed programs. The first Claude Code launch may take longer because TerraVision is downloaded and installed; the README recommends reconnecting from `/mcp` if the initial connection fails, or pre-installing it with `uvx`.

## Tools and capabilities

- Generate diagrams from natural-language cloud architecture descriptions.
- Render diagrams from Terraform code.
- Produce Terraform from a diagram-based design.
- Represent AWS, Azure, and Google Cloud architectures with provider-style icons.
- Show infrastructure boundaries such as VPCs, subnets, zones, and resource groups.
- Open generated images, edit them in draw.io, view their containing folder, and inspect their source from the Claude Desktop extension.

## Limitations and notes

Terraform is not required for description-based diagrams, but it is required for the Terraform input workflow. Graphviz is the drawing dependency, and platform-specific installation steps differ. Client behavior also varies: Claude Desktop displays diagrams in chat, while Claude Code saves them in the project’s `diagrams` folder.

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