Verified

envzero MCP Server

Env0 infrastructure deployment, logs, and Cloud Compass resource management via AI.

Data last scanned today · Reviewed today

15 1 dangerous tool13 tools★ 4TypeScriptApache-2.0

Overview

The env0 MCP Server enables AI agents to interface directly with the Env0 platform. By providing API credentials and an organization ID, users can facilitate natural language commands to deploy environments, cancel ongoing processes, and retrieve logs or resource data from Cloud Compass.

Our verdict

This server carries a high risk level (40/100) and is recommended only for users who can independently audit the code. The security score is primarily impacted by the lack of an editorial review, the fact that it is a community-maintained project rather than official vendor software, and the currently unreviewed status of its authentication mechanisms and read-only mode capabilities.

Uses only 8 direct dependencies for reduced supply-chain surface
Maintains an active development repository with recent commits
Provides documented setup instructions for major MCP clients

Community-maintained project lacking official vendor oversight
Authentication methods have not undergone security review
Read-only mode implementation status remains unverified

Setup

Claude Desktop

{
  "mcpServers": {
    "env0-mcp-server": {
      "args": [
        "-y",
        "@env0/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
get-projects	Get the projects from env0	low
get-environments	Get the environments from env0	low
deploy-environment	Creates a new deployment for an existing env0 environment. Always requires user to approve the deployment in env0.	medium
abort-environment	Abort an environment's current deployment	medium
approve-environment	Approve an environment plan, pending approval for applying.	medium
cancel-environment	Cancel an environment plan that is pending user approval.	medium
get-plan-logs	Get plan logs for a specific environment from env0	low
get-error-analysis	Analyzes errors in the last environment's deployment	low
get-deployment-context	Debug a past deployment by ID — metadata + steps + auto-picked step log	low
get-cloud-configurations	Get the compass cloud configurations	low

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What are the core technical requirements to run this server?

You must have Docker installed to run the server container, and you need an MCP-compatible client like Cursor, Claude Code, VSCode, Windsurf, Cline, Zed, or Augment Code.

›Do I always need to provide an Organization ID?

While it is specifically required if you belong to multiple organizations, providing the ID is recommended in all cases to ensure the server connects to the correct account.

›How do I authenticate the server with my env0 account?

You need to provide your env0 API key and secret as environment variables when configuring the Docker run command in your MCP client.

›Where can I find my env0 Organization ID?

You can find your Organization ID in the env0 dashboard by selecting Settings from the organization menu and checking the General tab under Organization Settings.