Zuul

Release clappingmonkey/zuul-mcp MCP server

A Model Context Protocol (MCP) server that enables AI applications like Claude to interact with Zuul CI/CD systems.

Features

• 29 MCP Tools for comprehensive Zuul interaction:

  • list_tenants - List all Zuul tenants
  • list_builds - Query builds with filters (project, pipeline, branch, result, etc.)
  • get_build - Get build details by UUID
  • get_build_logs - Get job output logs for a build
  • list_buildsets - Query buildsets with filters
  • get_buildset - Get buildset details by UUID
  • list_jobs - List jobs in a tenant
  • get_job - Get job details
  • get_job_variants - Get variant configurations for a specific job
  • list_pipelines - List pipelines
  • get_pipeline_status - Get current pipeline status including queue
  • list_projects - List projects
  • get_project - Get project details
  • get_tenant_status - Get overall tenant status
  • get_change_status - Get pipeline status for a specific change
  • get_config_errors - Get configuration errors
  • list_system_events - List system events (config updates, reconfigurations)
  • list_nodes - List nodepool nodes
  • list_labels - List available node labels
  • list_connections - List all Zuul connections
  • list_components - List all Zuul components (schedulers, executors, mergers, etc.)
  • list_semaphores - List semaphores
  • list_autoholds - List autohold requests (requires auth)
  • get_autohold - Get details of a specific autohold request
  • create_autohold - Create autohold request (requires auth)
  • delete_autohold - Delete autohold request (requires auth)
  • enqueue - Enqueue a change into a pipeline (requires auth)
  • dequeue - Dequeue a change or ref from a pipeline (requires auth)
  • promote - Promote changes to the top of a pipeline queue (requires auth)

• Multiple Transport Modes: stdio (for Claude Desktop), HTTP, and SSE

• Cross-Platform: Native binaries for Linux, macOS, and Windows

• Optional Authentication: JWT Bearer tokens for authenticated endpoints

Installation

Homebrew (macOS and Linux)

brew tap clappingmonkey/zuul-mcp
brew install zuul-mcp

Download Binary

Download the latest release for your platform from the releases page.

# Linux (amd64)
curl -LO https://github.com/clappingmonkey/zuul-mcp/releases/latest/download/zuul-mcp-linux-amd64
chmod +x zuul-mcp-linux-amd64
sudo mv zuul-mcp-linux-amd64 /usr/local/bin/zuul-mcp

# macOS (Apple Silicon)
curl -LO https://github.com/clappingmonkey/zuul-mcp/releases/latest/download/zuul-mcp-darwin-arm64
chmod +x zuul-mcp-darwin-arm64
sudo mv zuul-mcp-darwin-arm64 /usr/local/bin/zuul-mcp

# macOS (Intel)
curl -LO https://github.com/clappingmonkey/zuul-mcp/releases/latest/download/zuul-mcp-darwin-amd64
chmod +x zuul-mcp-darwin-amd64
sudo mv zuul-mcp-darwin-amd64 /usr/local/bin/zuul-mcp

Build from Source

# Requires Go 1.26+
go install github.com/clappingmonkey/zuul-mcp/cmd/zuul-mcp@latest

Configuration

Configuration can be done via environment variables or an env file:

Environment Variables

Variable	Required	Description
ZUUL_URL	Yes	Base URL of your Zuul instance (e.g., https://zuul.example.com)
ZUUL_DEFAULT_TENANT	No	Default tenant to use if not specified in tool calls
ZUUL_AUTH_TOKEN	No	JWT Bearer token for authenticated endpoints (autoholds)
ZUUL_TRANSPORT	No	Transport mode: stdio (default), http, or sse
ZUUL_HTTP_PORT	No	HTTP/SSE server port (default: 8080)

Using an Env File

You can use the --env-file flag to load configuration from a file instead of environment variables:

zuul-mcp --env-file /path/to/.env

The env file format is simple key-value pairs:

# .env.zuul
ZUUL_URL=https://zuul.example.com
ZUUL_DEFAULT_TENANT=openstack
ZUUL_AUTH_TOKEN=your-jwt-token

Note: Existing environment variables take precedence over values in the env file. This allows you to override specific settings without modifying the file.

Usage with Claude Desktop

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "zuul": {
      "command": "/usr/local/bin/zuul-mcp",
      "env": {
        "ZUUL_URL": "https://zuul.example.com",
        "ZUUL_DEFAULT_TENANT": "openstack"
      }
    }
  }
}

For authenticated operations (autoholds, queue management):

{
  "mcpServers": {
    "zuul": {
      "command": "/usr/local/bin/zuul-mcp",
      "env": {
        "ZUUL_URL": "https://zuul.example.com",
        "ZUUL_DEFAULT_TENANT": "openstack",
        "ZUUL_AUTH_TOKEN": "your-jwt-token"
      }
    }
  }
}

Alternatively, using an env file (useful for keeping secrets out of the config):

{
  "mcpServers": {
    "zuul": {
      "command": "/usr/local/bin/zuul-mcp",
      "args": ["--env-file", "/path/to/.env.zuul"]
    }
  }
}

Usage with HTTP Transport

For remote or web-based access:

# Start the server
ZUUL_URL=https://zuul.example.com ZUUL_TRANSPORT=http zuul-mcp

# Or with command line flags
zuul-mcp -transport=http -port=8080

Command Line Options

zuul-mcp [options]

Flag	Description
-env-file	Path to .env file for configuration
-transport	Transport mode: stdio (default), http, or sse
-port	HTTP/SSE server port (default: 8080)
-version	Show version information and exit

Example version output:

zuul-mcp 0.2.0 (abc1234) built on 2024-01-15T10:30:00Z

Example Prompts for Claude

Once configured, you can ask Claude questions like:

• "List all tenants in the Zuul instance"
• "Show me the recent failed builds for project openstack/nova"
• "What is the current status of the gate pipeline?"
• "What's the pipeline status for change 12345,1?"
• "Are there any configuration errors in the openstack tenant?"
• "Show me recent system events in this tenant"
• "Show me details of build UUID abc123..."
• "What Zuul components are running and are they healthy?"
• "Create an autohold for job my-failing-job in project my-project"
• "Show me details of autohold request 42"
• "What node labels are available in this tenant?"
• "Show me the variants for job build-container"
• "List all connections configured in Zuul"
• "What semaphores are defined in the tenant?"
• "Enqueue change 12345,1 into the gate pipeline for project my-project"
• "Promote changes 12345,1 and 13336,3 in the gate pipeline"

Development

This project uses Bazel for building, testing, and dependency management. No go.mod file is needed - all dependencies are declared in MODULE.bazel.

Prerequisites

• Bazel or Bazelisk (recommended)
• Go 1.26+ (for IDE support/gopls only - Bazel manages its own Go SDK)

Build

# Build the binary (development)
bazel build //cmd/zuul-mcp

# Build with version stamping (for releases)
bazel build //cmd/zuul-mcp --config=release

# The binary will be at:
# bazel-bin/cmd/zuul-mcp/zuul-mcp_/zuul-mcp

Test

# Run all tests
bazel test //...

Regenerate BUILD files

# After adding new Go files or packages
bazel run //:gazelle

Cross-Compile

# Linux amd64 (statically linked)
bazel build //cmd/zuul-mcp --config=linux_amd64

# Linux arm64 (statically linked)
bazel build //cmd/zuul-mcp --config=linux_arm64

# macOS amd64
bazel build //cmd/zuul-mcp --config=darwin_amd64

# macOS arm64 (Apple Silicon)
bazel build //cmd/zuul-mcp --config=darwin_arm64

# Windows amd64
bazel build //cmd/zuul-mcp --config=windows_amd64

Adding Dependencies

To add a new Go dependency:

1. Add the dependency using Go tooling:

   go get github.com/example/[email protected]
   go mod tidy
   

2. Update Bazel module configuration:

   bazel mod tidy         # auto-fix use_repo() if needed
   bazel run //:gazelle   # regenerate BUILD files
   

3. Verify everything works:

   bazel test //...
   

License

MIT License - see LICENSE for details.

Contributing

Contributions are welcome! See CONTRIBUTING.md for development setup and guidelines.

Security

To report a vulnerability, see SECURITY.md.