env0 MCP

env0 manages Terraform and OpenTofu deployments as governed environments, with plan approval, policy and cost controls, and a Cloud Compass inventory of what actually exists inside connected cloud accounts. The official MCP server exposes both halves of that product to an AI assistant, so infrastructure work can happen in the editor without giving up the approval gate. On the deployment side an agent can list projects, filter environments by id, name, or project, trigger a deployment, and then abort a running one or approve or cancel a pending plan. Diagnostic tools return plan logs from a dry run, a structured error analysis for a failed deployment, and full deployment context that bundles metadata, steps, and the relevant step log, which lets an assistant explain a failure rather than just report that one happened. On the inventory side it reads Cloud Compass configurations and filters discovered cloud resources by provider, region, or drift status, then generates Terraform or OpenTofu code for resources that are not yet under management, with a job status tool for tracking that generation. It runs against an env0 API key and works with the common MCP clients including Claude Code, Cursor, VS Code, and JetBrains assistants. The audience is platform and infrastructure engineers who want plan review, failure triage, and drift cleanup handled where they already write code.