hydra-mcp
Related Servers
Alternatives to hydra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to inspect and manage Hydra CI instances, including projects, jobsets, evaluations, builds, logs, queues, and authenticated actions such as triggering evaluations, controlling builds, and editing projects and jobsets.18MIT
- 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
- 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 gradedqualityAmaintenanceEnables AI assistants to interact with Jenkins servers through the Jenkins API, allowing them to browse items, nodes, views and plugins, inspect and control builds and queue items, retrieve artifacts, test reports and console output, submit pipeline inputs, and run Groovy scripts. Supports authenticated or anonymous access over stdio, SSE, and streamable-http transports with an optional read-only mode.-
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to inspect and operate a Jenkins instance — discovering jobs, views, nodes, and plugins; reviewing build chains, parameters, last-build status, console output, test reports, and artifacts; and triggering builds, stopping runs, or answering pipeline inputs. It connects over stdio, SSE, or streamable HTTP with optional credentials, read-only mode, and a credential-free health endpoint.311MIT
TDQS
Scored across 18 tools
Most tools target a distinct resource and action (e.g., list_projects vs get_project, get_build vs get_build_log). There is minor overlap between manage_eval and the individual restart_build/cancel_build/bump_build tools, and between get_job and get_build, but descriptions clarify the boundaries.
The set predominantly follows a verb_noun convention (list_instances, get_project, trigger_evaluation, put_jobset). Exceptions like 'search' (verb only) and 'manage_eval' (vague verb) are minor deviations but still readable.
18 tools is slightly heavy but justified by the breadth of the Hydra CI domain: instances, projects, jobsets, evaluations, builds, queue, search, and mutation actions. Each tool covers a meaningful operation without obvious redundancy.
The surface covers read and write operations for projects, jobsets, evaluations, and builds, including queue and search. Minor gaps exist—no delete operations for projects or jobsets, and no direct way to cancel an entire evaluation—but core workflows are well supported.