jenkins-mcp
Related Servers
Alternatives to jenkins-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely inspect and manage Jenkins servers, providing tools for jobs, builds, nodes, queues, views, plugins, artifacts, and Groovy scripts through natural-language workflows.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD systems for build management, job monitoring, console log analysis, and debugging through natural language commands.2MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD servers, including checking build status, triggering builds, and retrieving build logs.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD systems through natural language, providing build management, job monitoring, log analysis, and debugging capabilities.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityAmaintenanceEnables AI assistants to inspect and control Jenkins servers through the Jenkins API, covering jobs, nodes, queue items, builds, artifacts, views, plugins, and Groovy script execution. Supports read-only mode, credential-based or anonymous access, and multiple transports for secure, contextual interaction.-
TDQS
Scored across 22 tools
Each tool targets a distinct aspect of Jenkins (builds, queue, nodes, items, configs, console output). There is no overlap; even similar operations like get_build_console_chunk and get_build_console_tail are well-differentiated.
All tools use consistent snake_case verb_noun naming (e.g., get_build, cancel_queue_item, set_item_config). No mixing of styles or abbreviations.
22 tools is slightly high for a single server, but Jenkins is a complex system with many operations. The count is justified and not excessive, though it could be trimmed by combining some getters.
The tool set covers many operations (build, queue, nodes, configs, console, test reports) but lacks item creation/deletion and node creation/deletion. There are notable gaps in managing the lifecycle of items and nodes.