dramabox-jenkins-mcp
Related Servers
Alternatives to dramabox-jenkins-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Jenkins (with optional GitLab integration) that lets AI assistants list jobs, trigger and track deployments, fetch build logs, and verify whether tickets are deployed, without touching the Jenkins UI.17MIT
- AlicenseBqualityDmaintenanceA server that enables interaction with Jenkins CI/CD pipelines from any compatible MCP client (like Claude Desktop), allowing users to manage jobs, builds, coverage reports, and other Jenkins functionality through natural language.1113 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP server for Jenkins CI/CD integration that enables AI assistants to diagnose build failures, analyze pipelines, and search logs through natural conversation.6GPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables triggering Jenkins release and patch pipelines through natural language, with support for MCP and web interfaces.-
- AlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol (MCP) server that enables AI tools like chatbots to interact with and control Jenkins, allowing users to trigger jobs, check build statuses, and perform other Jenkins operations through natural language.MIT
- FlicenseAqualityDmaintenanceExposes a Jenkins controller's REST API to MCP-compatible clients, enabling job management, build triggering, and log retrieval through natural language.114-
TDQS
Scored across 3 tools
Each tool has a distinct, non-overlapping purpose: locating candidate jobs, checking deployment status, and triggering deployments. The clear separation makes it easy for an agent to select the right tool for each step.
Names follow a verb-based pattern with 'find_job' and 'get_status' using verb_noun, while 'deploy' is a bare verb. Minor inconsistency but still predictable and readable.
Three tools is an ideal, focused set for the server's purpose of Jenkins deployment management. Each tool is essential and there is no bloat.
The set covers the core workflow: find a job, inspect its status, and deploy. It lacks an explicit cancel or rollback operation, but for the stated purpose of locating, checking, and deploying, coverage is solid.