MCP.Market

Zuul MCP server

by imatza-rh·io.github.imatza-rh/mcp-zuul·v0.11.0·21 stars
No reviews yet

Zuul CI — build failure analysis, log search, pipeline status, and job configuration

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

21 stars61 downloads/wk

Reviews

Write one

Nobody has reviewed Zuul yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Zuul tools (49, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • autohold_createwrite action

    Create an autohold request — hold nodes after a job failure for debugging.

  • autohold_deletewrite action

    Delete an autohold request.

  • batch_diagnose

    Classify multiple failed builds in one call — returns a triage table.

  • browse_build_logs

    Browse or fetch files from a build's log directory.

  • check_health

    Test Zuul API connectivity and auth status.

  • dequeuewrite action

    Remove a change or ref from a pipeline.

  • diagnose_and_test

    One-call diagnosis + test results — combines diagnose_build and get_build_test_results.

  • diagnose_build

    One-call failure diagnosis — structured failures + relevant log context.

  • enqueue

    Enqueue a change or ref into a pipeline for testing.

  • find_flaky_jobs

    Detect flaky jobs by analyzing recent build history for intermittent failures.

  • get_autohold

    Get details of a specific autohold request.

  • get_badge

    Get a status badge URL (SVG) for a project's latest buildset result.

  • get_build

    Get build details — log URL, nodeset, artifacts, timing, error detail.

  • get_build_anomalies

    Detect anomalous log lines using LogJuicer ML-based analysis.

  • get_build_failures

    Analyze a failed build — which task failed, on which host, with error message.

  • get_build_log

    Read, search, and navigate build log files with grep, line ranges, and error summary.

  • get_build_test_results

    Parse JUnit XML test results from a build's log directory.

  • get_build_times

    Build duration trends — compute avg/min/max to detect performance regressions.

  • get_buildset

    Get buildset details — result, pipeline, project, change.

  • get_change_status

    Pipeline status for a specific change or PR/MR.

  • get_components

    Show Zuul system components — schedulers, executors, mergers, web servers.

  • get_config_errors

    Get Zuul configuration errors — broken configs, missing refs, syntax errors.

  • get_connections

    List configured source connections — Gerrit, GitHub, GitLab instances.

  • get_freeze_job

    Get fully-resolved job configuration after inheritance.

  • get_freeze_jobs

    Get the resolved job graph for a pipeline/project/branch.

  • get_job

    Get job configuration — parent, nodeset, timeout, branches, and all variants.

  • get_job_durations

    Get avg/min/max duration for multiple jobs in a single call.

  • get_project

    Get project configuration — which pipelines and jobs are configured.

  • get_status

    Live pipeline status showing what's currently queued/running.

  • get_tenant_info

    Get tenant capabilities, auth config, and websocket URL.

  • investigate_change

    One-call investigation — builds + diagnosis + autohold status for a change.

  • list_autoholds

    List autohold requests — nodes held after failure for debugging.

  • list_builds

    Search builds with filters. Returns compact build summaries.

  • list_buildsets

    Search buildsets (groups of builds triggered by a single event).

  • list_images

    List nodepool disk images with build status and upload artifacts.

  • list_jobs

    List all jobs in a tenant. Optionally filter by name substring.

  • list_labels

    List available nodepool labels (node types that jobs can request).

  • list_nodes

    List nodepool nodes — available, in-use, or provisioning.

  • list_pipelines

    List all pipelines with their trigger types.

  • list_projects

    List all projects in a tenant. Optionally filter by name substring.

  • list_providers

    List nodepool cloud providers with flavors and images.

  • list_semaphores

    List semaphores — resource locks that limit concurrent job execution.

  • list_system_events

    List system events — config updates, reconfigurations, pipeline changes.

  • list_tenants

    List all Zuul tenants with project and queue counts.

  • main
  • promote

    Promote changes to the top of a pipeline queue.

  • reenqueue_buildset

    Re-enqueue a buildset — re-triggers a previous buildset's pipeline run.

  • stream_build_console

    Read live console output from a RUNNING build via WebSocket.

  • tail_build_log

    Get the last N lines of a build log — fastest way to see why a build failed.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan29 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Zuul compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,113 Developer tools servers
Tools
49
the typical Developer tools server has 8
Tools that change things
6%
typical: 6%. Fewer write tools means less an agent can break
GitHub stars
21
more than 87% of 857 Developer tools servers
Downloads a week
61
more than 34% of 510 Developer tools servers with a package

What its tools let an agent do: 46 read · 3 change

Install Zuul in Claude Code, Cursor or VS Code

claude mcp add mcp-zuul -- uvx mcp-zuul
Add to Cursor

What the publisher says

From the Zuul repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.imatza-rh/mcp-zuul -->

mcp-zuul

Debug build failures by asking questions, not clicking through web UIs. An MCP server for Zuul CI.

If mcp-zuul saves you a debugging session, a ⭐ star helps others find it.

One command, no install:

claude mcp add zuul -e ZUUL_URL=https://your-zuul.example.com -- uvx mcp-zuul

48 tools, 5 prompts, 3 resources — covering builds, logs, pipelines, jobs, infrastructure, and live status. Works with Claude Code, Claude Desktop, Cursor, Codex, Windsurf, and any MCP-compatible client.

Why mcp-zuul?

Quick Start

uvx (no install, recommended):

claude mcp add zuul \
               -e ZUUL_URL=https://softwarefactory-project.io/zuul \
               -e ZUUL_DEFAULT_TENANT=rdoproject.org \
               -- uvx mcp-zuul

pip:

pip install mcp-zuul

Docker:

docker build -t mcp-zuul .

LobeHub — send this to your AI agent:

Read https://lobehub.com/mcp/imatza-rh-mcp-zuul/skill.md and follow the instructions to install the MCP server.

See Setup for full configuration options including Kerberos and multi-instance.

Features

Structured failure analysis — getbuildfailures parses Zuul's job-output.json and returns exactly which Ansible task failed, on which host, with error message, return code, and stderr. No log scrolling needed.

Read any log file — getbuildlog isn't limited to job-output.txt. Pass logname to read any file in the build's log directory (ciscript logs, ansible.log, deployment logs) with full grep, tail, and line-range support.

Precise log navigation — Jump to exact line ranges with startline/endline. After finding an error at line 6148, read lines 6130-6160 instead of scrolling through 200-line chunks.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Zuul: common questions

Is Zuul MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Zuul safety report
How do I install Zuul?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Zuul need an API key?
No secret keys are declared. It reads 7 settings from the environment.
Is Zuul maintained?
The last commit was 14 days ago (2026-11-01). The latest release is v0.11.0.
What can I use instead of Zuul?
Servers from other publishers that do the same job: GitLab MCP Server, walkerOS Flow MCP server and Grasp — Code Architecture & Dependency Analysis MCP server.
How does Zuul compare with other Developer tools MCP servers?
safety score 92/100 (higher than 90% of 1,113 Developer tools servers); tools 49 (the typical Developer tools server has 8); tools that change things 6% (typical: 6%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Zuul

Same job from other publishers: the closest match first, then the best rated.

  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • walkerOS Flow
    Build, validate, simulate, and deploy walkerOS event pipelines
    B
  • Grasp — Code Architecture & Dependency Analysis
    Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
    C
  • GitLab
    GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
    B
  • Suvadu
    Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
    A