mcp-jenkins
Related Servers
Alternatives to mcp-jenkins
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI language models to securely interact with Jenkins through the Model Context Protocol, exposing tools for jobs, builds, nodes, queues, views, plugins, artifacts, and Groovy scripts.-
- FlicenseNot gradedqualityAmaintenanceEnables AI language models to securely interact with Jenkins through the Model Context Protocol, exposing tools to query and manage items, nodes, queues, builds, artifacts, views, plugins, and execute Groovy scripts while maintaining data privacy and security.-
- FlicenseNot gradedqualityAmaintenanceEnables AI language models to interact securely with Jenkins through the Model Context Protocol, supporting job, build, queue, node, view, plugin, artifact, and Groovy script operations while maintaining data privacy and security.-
- FlicenseNot gradedqualityAmaintenanceEnables AI language models to securely interact with Jenkins through the Model Context Protocol, exposing tools for querying and managing jobs, builds, nodes, queues, views, plugins, artifacts, and Groovy scripts.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Jenkins through the Model Context Protocol, providing secure, configurable tools to inspect and manage jobs, builds, nodes, queues, artifacts, views, plugins, and Groovy scripts.-
- FlicenseNot gradedqualityAmaintenanceEnables secure, contextual AI interactions with Jenkins by exposing tools for jobs, builds, nodes, queues, views, plugins, and Groovy scripts through the Model Context Protocol.-
TDQS
Scored across 36 tools
Most tools target distinct resources and actions, and descriptions actively disambiguate near-neighbors (e.g. get_build_test_report warns to use get_build_test_failures instead, get_pending_inputs/submit_input explain their relationship). Minor overlap remains between get_all_items/query_items and among the many get_build_* variants, but the naming and args keep them separable.
Strong dominant verb_noun pattern (get_build, set_item_config, build_item, stop_build, cancel_queue_item, run_groovy_script). Slight inconsistencies appear in the get_all_X vs query_items vs get_item phrasing and get_build_artifact vs get_all_build_artifacts, but overall the convention is predictable.
36 tools is on the heavy side and exceeds the typical comfortable range. Jenkins genuinely spans many sub-domains (builds, items, nodes, plugins, queue, views, groovy), so most tools earn their place, but the surface is large enough to feel bloated and harder to navigate.
Coverage is broad: build lifecycle (get/stop/console/tests/params/artifacts), item config and triggering, node config, plugin inspection with dependency graphs, queue management, views, and an escape-hatch groovy script. Missing item/node create-delete operations are minor gaps an agent can work around via groovy or config setters.