Skip to main content
Glama
imatza-rh

mcp-zuul

by imatza-rh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-zuul

No user-submitted related servers found.

    Related Servers

    • zuul-mcp

      clappingmonkey
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Zuul CI/CD with 25 tools for builds, pipelines, queue management (enqueue/dequeue/promote), infrastructure visibility, and autohold management. Supports stdio, HTTP, and SSE transports.
      MIT

    • azure-devops-local-mcp

      Laonnda
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.
      30
      MIT

    • mcp-server-logs-sieve

      Oluwatunmise-olat
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects Claude (or any MCP compatible client) to your existing log infrastructure. Query, summarize, and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki, and Elasticsearch without writing filter expressions or leaving your editor.
      204 npm
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 44 tools

    Disambiguation3/5

    There is meaningful overlap among the many diagnostic tools: get_build_failures vs diagnose_build, get_build_log vs tail_build_log, and batch_diagnose vs diagnose_and_test can easily cause misselection. Descriptions do clarify intended use, but the number of near-purposed tools makes the distinction harder than it should be.

    Naming Consistency4/5

    Most tools follow a clean snake_case verb_noun pattern such as list_builds, get_build, create_autohold. Minor deviations like autohold_create, autohold_delete, batch_diagnose, and diagnose_and_test break the strict pattern but are still readable and predictable.

    Tool Count2/5

    44 tools is far beyond the 3-15 well-scoped range, even for a broad CI/CD monitoring server. Many tools exist only as convenience wrappers or duplicates, which inflates the surface and forces agents to spend time choosing between overlapping options.

    Completeness3/5

    The server covers a wide range of Zuul operations: build details, buildsets, logs, failures, test results, nodes, autoholds, configuration errors, and pipeline status. However, mutating lifecycle operations other than autoholds are absent—there is cancel/re-enqueue build, no job update, and no way to drive pipeline actions—so agents can hit dead ends in operational workflows.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources