This MCP server facilitates interaction with Zuul CI, allowing users to debug build failures through structured queries instead of navigating web interfaces.
From the registry: Zuul CI — build failure analysis, log search, pipeline status, and job configuration
Please install the `mcp-zuul` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Zuul instance URL** — Base URL of a Zuul CI instance
Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["mcp-zuul"]
- required environment variables:
- `ZUUL_URL`: Zuul base URL (example: `https://softwarefactory-project.io/zuul`)
- optional environment variables:
- `ZUUL_DEFAULT_TENANT`: Default tenant (saves passing tenant on every call) (example: `rdoproject.org`)
- `ZUUL_AUTH_TOKEN`: Bearer token for authenticated instances (example: `<your-token>`)
- `ZUUL_USE_KERBEROS`: Enable Kerberos/SPNEGO auth (example: `false`)
- `ZUUL_READ_ONLY`: Set to false to enable write operations (example: `true`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.ZUUL_URLrequiredZuul base URL (e.g. https://softwarefactory-project.io/zuul)Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.