mcp-zuul: Instructions file for Claude Code

CLAUDE.md

mcp-zuul CLAUDE.md is an instructions file for Claude Code from imatza-rh/mcp-zuul. It costs 2,037 tokens per session, scanned A, original, Apache-2.0.

A repository instruction file for mcp-zuul, an MCP server that lets coding agents access Zuul CI build data, logs, jobs, pipelines, infrastructure, and live status.

In plain words
What is it for?
Use it when developing or maintaining mcp-zuul, including running it locally or validating changes.
Why use it?
It gives agents the project context and the exact commands needed to install dependencies, run the server, test, format, lint, and check types.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is imatza-rh/mcp-zuul's own configuration. It tells Claude Code how to work on mcp-zuul itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-zuul configures →

Reuse

Borrowing it

Nothing to install: this file belongs to imatza-rh/mcp-zuul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/imatza-rh/mcp-zuul/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/imatza-rh/mcp-zuul

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-zuul CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/imatza-rh/mcp-zuul/claude-md/github.svg)](https://agentmods.dev/instructions/imatza-rh/mcp-zuul/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/imatza-rh/mcp-zuul/claude-md"><img src="https://agentmods.dev/badge/instructions/imatza-rh/mcp-zuul/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-zuul CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/imatza-rh/mcp-zuul/claude-md"><img src="https://agentmods.dev/badge/instructions/imatza-rh/mcp-zuul/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,037 This file is loaded in full into every session.
When invoked 2,037 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.02037 $0.02037
Opus 5 $0.01019 $0.01019
Sonnet 5 $0.00407 $0.00407
Haiku 4.5 $0.00204 $0.00204

Measured 9d ago against content hash bbbb84be4671, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

mcp-zuul CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What This Is

MCP server for Zuul CI — 48 tools (40 read-only + 6 write + 1 LogJuicer + 1 console stream), 5 prompts, and 3 resources exposing builds, logs, pipelines, jobs, infrastructure, and live status via the Model Context Protocol. Published on PyPI as mcp-zuul. Supports stdio, SSE, and streamable-http transports.

Commands

# Install dev dependencies
uv sync --extra dev

# Run the server locally
ZUUL_URL=https://softwarefactory-project.io/zuul uv run mcp-zuul

# Tests
uv run pytest tests/ -v                    # all tests
uv run pytest tests/test_tools_builds.py -v  # single test file
uv run pytest tests/ -v -k "test_name"     # single test by name

# Lint and format
uv run ruff check src/ tests/
uv run ruff format --check src/ tests/     # check only
uv run ruff format src/ tests/             # auto-fix

# Type check
uv run mypy src/mcp_zuul/

Architecture

All source lives in src/mcp_zuul/. The package uses hatchling as build backend with src layout.

Module Dependency Flow

__init__.py        →  imports tools, prompts, resources (registers decorators), exports main()
server.py          →  MCPServer instance ("zuul-ci"), lifespan (creates httpx clients), _BearerAuth
tools/             →  Package: 47 @mcp.tool() functions split by domain
  __init__.py      →  Re-exports for backward compat (tests import from mcp_zuul.tools)
  _common.py       →  Shared constants, _check_url_host(), _resolve(), _fetch_job_output(), re-exports from parsers
  _builds.py       →  8 build tools: list_builds, get_build, get_build_failures, diagnose_build, batch_diagnose, diagnose_and_test, etc.
  _console.py      →  1 console stream tool: stream_build_console (optional, requires websockets)
  _logs.py         →  3 log tools: get_build_log, browse_build_logs, tail_build_log
  _status.py       →  7 status/analytics: list_tenants, get_status, get_change_status, find_flaky_jobs, etc.
  _config.py       →  15 config/infra: list_jobs, get_job, get_project, list_nodes, get_freeze_job, etc.
  _write.py        →  6 write ops: enqueue, dequeue, autohold_create, autohold_delete, promote, reenqueue_buildset
  _tests.py        →  1 test results: get_build_test_results + JUnit XML parsing
  _logjuicer.py    →  1 LogJuicer: get_build_anomalies
prompts.py         →  5 @mcp.prompt() templates (debug_build, compare_builds, check_change, tenant_health, diagnose_queue_delay)
resources.py       →  3 @mcp.resource() templates (zuul://{tenant}/build|job|project/...)
helpers.py         →  AppContext dataclass, api() HTTP wrapper, parse_zuul_url(), utility functions
config.py          →  Config dataclass loaded from env vars (ZUUL_URL, MCP_TRANSPORT, ZUUL_ENABLED_TOOLS, etc.)
auth.py            →  Kerberos/SPNEGO authentication (drives OIDC redirect chain)
parsers.py         →  parse_playbooks(), smart_truncate(), extract_inner_recap(), extract_inner_failures(), extract_errors(), grep_log_context()
formatters.py      →  Token-efficient formatters (fmt_build, fmt_buildset, fmt_project, fmt_job_variants, etc.)
errors.py          →  @handle_errors decorator wrapping all tools with uniform error→JSON handling
classifier.py      →  Failure classification (INFRA_FLAKE, REAL_FAILURE, CONFIG_ERROR, UNKNOWN)

Read the full file on GitHub · 109 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 109 lines · 2,037 tokens per session scan A bbbb84be4671

Subscribe to this mod's changes

mcp-zuul CLAUDE.md is an instructions file published in the GitHub repository imatza-rh/mcp-zuul (20 stars, last pushed 4d ago), licensed Apache-2.0. It adds 2,037 tokens to every session, about $0.0102 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens