Zuul CI — build failure analysis, log search, pipeline status, and job configuration
Zuul CI — build failure analysis, log search, pipeline status, and job configuration. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
47 tools, 3 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.
The server publishes 3 tools. What each one is for:
Buildsets — The Buildsets tool exposed by this serverInfrastructure — The Infrastructure tool exposed by this serverArchitecture — The Architecture tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at mcp-zuul on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: ZUUL_URL, ZUUL_DEFAULT_TENANT, ZUUL_USE_KERBEROS, ZUUL_VERIFY_SSL, ZUUL_AUTH_TOKEN, LOGJUICER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Buildsets, Infrastructure, Architecture — is a fair guide to whether it matches your workflow. It is maintained by imatza-rh; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Buildsets | The Buildsets tool exposed by this server. |
| Infrastructure | The Infrastructure tool exposed by this server. |
| Architecture | The Architecture tool exposed by this server. |
{
"mcpServers": {
"zuul": {
"command": "uvx",
"args": ["mcp-zuul"],
"env": {
"ZUUL_URL": "https://softwarefactory-project.io/zuul",
"ZUUL_DEFAULT_TENANT": "rdoproject.org"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ZUUL_URL | Endpoint or connection string the server talks to. | Yes |
| ZUUL_DEFAULT_TENANT | Configuration value read at startup. | Optional |
| ZUUL_USE_KERBEROS | Configuration value read at startup. | Optional |
| ZUUL_VERIFY_SSL | Configuration value read at startup. | Optional |
| ZUUL_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| LOGJUICER_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.