hydra-mcp
Related Servers
Alternatives to hydra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to inspect and manage the Nix CI server's projects, jobsets, evaluations, builds, build steps, logs, and queue across multiple instances, and with credentials trigger evaluations, restart or cancel or bump builds, and create or edit projects and jobsets.18MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and operate Jenkins instances: listing jobs, builds, queue items and nodes, reading incremental build logs and pipeline stage views, and triggering, stopping or cancelling builds with read-only guards.1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely interact with Jenkins through its API, exposing tools for inspecting items, nodes, views, queues, and builds, reading console output, test reports, and artifacts, managing plugins, and triggering, stopping, or approving pipeline builds, including executing Groovy scripts. Supports stdio, SSE, and streamable-HTTP transports with configurable authentication, SSL verification, and a read-only mode.-
- FlicenseNot gradedqualityAmaintenanceEnables AI models to securely inspect and operate Jenkins through tools for jobs, builds, queue items, nodes, views, plugins, artifacts, pipeline inputs, and Groovy script execution. Supports stdio, SSE, and streamable-HTTP transports with configurable authentication and a read-only mode.-
- FlicenseNot gradedqualityFmaintenanceEnables LLMs to access Jenkins job data, trigger builds, and manage Jenkins tasks through a standardized interface.5-
TDQS
Scored across 18 tools
Most tools target a distinct resource+action (project, jobset, eval, build, queue, log), and descriptions clarify the read vs write split. There is mild overlap between the single-build write tools (restart_build, cancel_build, bump_build) and the bulk manage_eval, and between get_job and get_build, but the descriptions make the intended selection clear.
Nearly all tools follow verb_noun snake_case (list_projects, get_build, trigger_evaluation, cancel_build), which is predictable. Minor deviations are the bare 'search' (no noun) and the vague 'manage_eval', plus 'put_*' being used for create-or-update semantics.
18 tools is on the heavy side but each maps to a real Hydra concept (instances, projects, jobsets, evals, builds, queue, logs, search) plus a small write set. Nothing looks redundant enough to cut, though the read surface could be consolidated slightly.
Coverage is strong for the CI lifecycle: discovery, project/jobset inspection and editing, evaluations, builds, logs, queue control, and build restart/cancel/bump. Gaps are minor—no delete operations for projects, jobsets, or builds, and no tool to fetch build output/product contents beyond the log tail.