ZenOps

ZenOps is a data-driven operational query tool that exposes multiple access methods for querying cloud resources, CI/CD tooling, and other operational data. It supports a unified MCP protocol proxy, a RESTful HTTP API, a command-line interface (CLI) built on Cobra, and a web frontend. Through MCP, you can configure external MCP clients to route queries to ZenOps and receive structured responses. The project also provides integrations with chat tools (DingTalk, Feishu, and WeChat) for conversational, streaming query results, enabling operators to ask questions in natural language and receive live updates.

To use ZenOps, deploy it via Docker as shown in the quick-start guide. Once running, open the frontend at http://localhost:8080 to configure cloud vendors, CI/CD connectors (e.g., Jenkins), and LLM/IM credentials. You can use the HTTP API to programmatically query resources, the CLI for local scripted queries, or the MCP interface to connect external MCP clients. The MCP support allows external systems to proxy queries through ZenOps, enabling centralized access to multi-cloud resources and automation tooling within your environment.

Prerequisites:

• Docker installed and running on your host
• Access to the internet to pull the ZenOps image

Step-by-step installation:

1. Install Docker (if not already installed):

   • macOS: https://docs.docker.com/desktop/mac/
   • Windows: https://docs.docker.com/desktop/windows/
   • Linux: follow your distro's instructions (e.g., apt/yum install docker)

2. Run ZenOps with Docker (quick-start):

# Deploy ZenOps in detached mode with ports and data volume
docker run -itd \
  --name zenops \
  -p 8080:8080 \
  -p 8081:8081 \
  -v ./data:/app/data \
  docker.cnb.cool/opsre/zenops

3. Verify startup:

docker ps | grep zenops

4. Access the UI/API:

• Frontend: http://localhost:8080
• Admin default credentials (per README): admin/admin123

Tips and common issues:

• The MCP proxy is enabled by default after the container starts; you can configure external MCP clients to route queries to ZenOps.
• If you change configuration in the UI, ensure the ZenOps container has access to the updated credentials/keys and that network access to required cloud APIs is allowed.
• When upgrading, pull the latest image and recreate the container while preserving the ./data volume to keep configurations and state.
• If you run into port conflicts, adjust the -p mappings in the docker run command to free up required ports.
• Environment variables are commonly used to inject API keys or toggles; this container reads configuration from its mounted volume and its web UI settings.