Get the compass cloud configurations

Get the environments from env0

Get the projects from env0

Approve an environment

Cancel an environment

Abort an environment

Get cloud resources from env0

Generate Infrastructure as Code (IaC) for cloud resources. This tool initiates a long-running job and returns a job ID for tracking progress.

Check the status and retrieve results of an Infrastructure as Code generation job. Use this tool after calling generate-iac to monitor progress and get results. Could take up to around 1 minute to get results.

This tool creates a new deployment for an existing env0 environment. You can use the "get-environments" or "get-environment" tool to find the environment ID of the environment you are looking for. This action ALWAYS requires approval from the user before execution.

Get plan logs for the latest deployment of a specific environment from env0. For historical deployments use get-deployment-context instead. For full plan see env0 console.

Analyzes errors in the latest deployment of an environment. For historical deployments use get-deployment-context instead.

Find recent deployments for an environment, optionally filtered by status. Use this to pick a deploymentLogId for follow-up debug via get-deployment-context.

Use when: user asks for deployment history, wants to find a failed deployment, or needs to pick among multiple recent deployments.

Do NOT use for the latest deployment alone — get-plan-logs or get-error-analysis already cover that without needing an ID.

Returns up to 10 deployments by default (raise limit to 25 max). Sorted newest-first. Each entry includes: id, status, type, queuedAt, startedAt, finishedAt, triggerName, comment, resourceCount, blueprintRevision, blueprintName, blueprintType, prNumber, gitMetadata, planSummary, failedCommand. Set hasMore=true means another page exists.

Prefer filtering via 'statuses' over paging with 'offset'.

Fetch debug context for one specific deployment: metadata, all step statuses, and the log of the first failed step (auto-picked: status FAIL or TIMEOUT). Returns log:null on clean success — pass an explicit stepName to inspect a successful step.

Use when: user asks why a past deployment failed, names a deploymentLogId, or wants to inspect a specific step (apply, destroy, custom flow) of a historical deployment.

Do NOT use for the latest deployment's plan log — use get-plan-logs (no deploymentLogId needed, cheaper). For an error summary use get-error-analysis.

deploymentLogId is REQUIRED. Use search-deployments first to find one.

Returns { deployment, steps, log }. log is { stepName, events, truncated } or null when no failed step exists and no stepName was given. Step names look like 'tf:plan', 'tf:apply', 'opentofu:plan', 'terragrunt:plan', 'pulumi:preview', 'helm:diff', 'k8s:apply', 'git:clone', 'spec:load'. Targeting a NOT_STARTED step returns 400.

Example chain: search-deployments(envId, statuses="FAILURE") → get-deployment-context(deploymentLogId=)