Jenkins MCP

The MCP Server plugin turns a Jenkins controller into an MCP endpoint, so AI clients can talk to Jenkins over the protocol instead of scraping the web UI or hand rolling REST calls. Job tools cover getJob and getJobs for configuration and listing, triggerBuild for starting builds including parameterized ones, and getQueueItem for checking what is waiting to run. Build tools include getBuild for build metadata, getBuildLog and searchBuildLog for reading and searching console output, updateBuild for editing build metadata such as display name and description, and getTestResults for test execution data. A second group targets pipeline debugging. rebuildBuild reruns a build with its original parameters, getReplayScripts returns the pipeline scripts used for a build, and replayBuild reruns it with a modified script, which is how an agent can propose and test a pipeline fix without committing it first. Source control tools getJobScm, getBuildScm, getBuildChangeSets and findJobsWithScmUrl connect builds back to repositories, changes and commits. whoAmI and getStatus identify the authenticated user and report controller health. The plugin installs like any other Jenkins plugin and authenticates with a per user API token over HTTP basic auth, so every call is subject to the same role based permissions the user already has in Jenkins. It suits DevOps engineers and developers who want a coding assistant to read a failing build log, correlate it with the commit that caused it, and rerun the job without leaving the editor.