Skip to main content
The env zero MCP server lets AI assistants and IDEs that support the Model Context Protocol (MCP) work with env zero: list projects and environments, deploy and approve, read deployment history and logs, and generate code for cloud resources. The server is open source: env0/mcp-server.

Prerequisites

  • Docker. The server runs as the env0/mcp-server container image.
  • An env zero API key: its key ID and secret.
  • Your Organization ID, if the API key has access to more than one organization.

Configure your client

Add the server to your MCP client. Replace the placeholders with your API key ID, API key secret, and Organization ID. Omit the ENV0_ORGANIZATION_ID line if the key has access to only one organization.
Most other clients accept the same mcpServers JSON. For client-specific instructions, see the env0/mcp-server README. Each server instance uses one API key. To work with keys that have different permissions, add the server more than once under different names.

Environment variables

Tools

To investigate an older failed deployment, the assistant can call search-deployments with statuses set to FAILURE, then pass a returned deployment ID to get-deployment-context.

Permissions

The tools run with the permissions of the API key. A tool that needs a permission the key does not have fails. deploy-environment always waits for approval, and approve-environment can give that approval if the key has the permission to approve. For read-only use, use a Read-only API key. get-error-analysis requires access to AI-Powered Error Insights. The cloud resource tools require Cloud Compass.

Troubleshooting

Next steps