mcp

The Env0 MCP Server enables AI coding assistants and chatbots to perform actions against Env0 resources directly from natural language prompts. By running the Docker container with the required Env0 API credentials, the MCP server exposes a context-aware interface that lets AI agents deploy, cancel, fetch logs for environments, and retrieve resources via Env0's Cloud Compass. This empowers your AI tools to manage cloud environments and infrastructure tasks within Env0 through MCP-compatible clients.

To use it, start the MCP server container with your API key, secret, and organization ID. Then configure your MCP client (Cursor, Claude Code, Windsurf, VS Code, Zed, JetBrains AI, etc.) to point at the env0 MCP server using the provided docker command. Once configured, you can issue natural language requests like: determine the status of an environment, deploy a new environment, fetch logs, or query Cloud Compass resources. The MCP server translates these requests into Env0 API calls and returns structured results suitable for the chat/AI agent to present to you.

Prerequisites:

• Docker installed on your machine or host where you will run the MCP server container
• Env0 API Credentials (API Key, API Secret) and Organization ID
• Access to a MCP-compatible client (Cursor, Claude Code, VS Code, Windsurf, Cline, Zed, JetBrains AI, etc.)

Step 1: Prepare Env0 credentials

• Obtain your Env0 API Key and API Secret from the Env0 API Keys guide.
• Ensure you know your Organization ID from the Env0 dashboard.

Step 2: Run the MCP server (Docker)

• Replace the placeholders with your actual credentials and organization ID:

# Example run command
docker run -i --rm \
  -e ENV0_API_KEY=your-api-key-here \
  -e ENV0_API_SECRET=your-api-secret-here \
  -e ENV0_ORGANIZATION_ID=your-org-id-here \
  env0/mcp-server

Step 3: Connect your MCP client

• In Cursor, Claude Code, Windsurf, VS Code, or other MCP clients, add a new MCP server configuration pointing to the running container as described in the README integration guides for your client. The core setup will reference the same environment variables used when starting the container.
• If your client requires explicit host/port, provide the container host (e.g., localhost) and the port exposed by the MCP server as per your client's documentation.

Step 4: Verify and test

• Send a basic natural language request like “List environments in my organization” to verify the MCP connection and permissions.
• Review the results and refine prompts or permissions if needed.

Tips:

• Keep your Env0 API credentials secure; do not commit them to code repositories.
• If you belong to multiple organizations, ensure you provide the correct ENV0_ORGANIZATION_ID to route requests properly.
• The docker-based setup is flexible for local development and CI; ensure the host has network access to Env0 APIs.
• If you encounter authentication errors, re-validate API keys and secrets in the Env0 dashboard and ensure they’re correctly exported to the container.
• This MCP server relies on the standard MCP workflow supported by Env0 resources and Cloud Compass; consult client-specific docs if you’re using advanced features.
• For production, consider running the container with appropriate resource limits and secrets management (e.g., Docker secrets or environment management in your orchestration platform).