Jenkins MCP Server, the official Jenkins plugin

• Lists your Jenkins jobs, a page at a time

  Returns a list of jobs, sorted by name and split into pages, optionally inside a folder.

  Try: “List all jobs in the payments folder”

  Read · getJobs

• Shows one job's details and its latest builds

  Fetches a job by its full path, with its status and recent build info.

  Try: “Show me the details of the deploy-prod job”

  Read · getJob

• Finds jobs that build from a given Git repository

  Searches for jobs whose source settings point at the Git repository address you give.

  Try: “Which Jenkins jobs build github.com/acme/api?”

  Read · findJobsWithScmUrl

• Shows a build's result, timing and details

  Retrieves a specific build, or the last build, of a job, with its result and key details.

  Try: “Did the last build of my-service pass?”

  Read · getBuild

• Reads a build's console log, page by page

  Returns lines from a build's log, from the start or the end, and can keep reading as a running build writes more.

  Try: “Show the last 200 lines of the log for build 512 of my-service”

  Read · getBuildLog

• Searches a build's log for a word or pattern

  Finds log lines that match text or a regular expression, and returns quickly even while the build is still running.

  Try: “Search the last build log of my-service for OutOfMemoryError”

  Read · searchBuildLog

• Summarizes a build's test results and failing tests

  Returns pass, fail and skip counts plus each failing test with its message and how many builds in a row it has failed. Can return full records on request.

  Try: “Which tests failed in the last build of my-service?”

  Read · getTestResults

• Lists tests that failed and then passed on retry

  Returns the flaky tests from a build: those that failed at least once and passed on a later attempt, with each failure's message.

  Try: “Which tests were flaky in yesterday's nightly build?”

  Read · getFlakyFailures

• Shows the code changes that went into a build

  Retrieves the commits and change log included in a specific build.

  Try: “What commits went into build 512 of my-service?”

  Read · getBuildChangeSets

• Shows a job's source code settings

  Returns the repository and branch settings configured for a job.

  Try: “Which repository and branch does the release job use?”

  Read · getJobScm

• Shows the source code settings used by one build

  Returns the repository settings recorded for a specific build.

  Try: “Which branch did build 512 check out?”

  Read · getBuildScm

• Checks a queued build's status by its ID

  Looks up an item in the build queue, for example to see whether a build you just triggered has started.

  Try: “Has the build I just queued started yet?”

  Read · getQueueItem

• Starts a build of a job, with parameters if needed

  Schedules a new build of a job and returns its place in the queue. Parameterized jobs accept values such as branch or environment; file parameters are not supported.

  Try: “Run the deploy-staging job with BRANCH=main”

  Runs code · triggerBuild

• Runs a build again with the same parameters

  Re-runs a build, by default the last one, using the same parameters; Pipeline jobs reuse the original script.

  Try: “Rebuild the last failed build of my-service”

  Runs code · rebuildBuild

• Shows the Pipeline script a build ran

  Returns the main and loaded scripts of a replayable Pipeline build, so they can be inspected or changed before a replay.

  Try: “Show me the Pipeline script used by build 88 of release”

  Read · getReplayScripts

• Re-runs a Pipeline build with a changed script

  Runs a Pipeline build again using a modified script you provide, if replay is allowed for you.

  Try: “Replay the last release build with the test stage skipped”

  Runs code · replayBuild

• Stops a running build or removes one from the queue

  Cancels a build that is running or waiting in the queue.

  Try: “Cancel the running build of deploy-prod”

  Write · cancelBuild

• Creates a new Pipeline job from a script

  Makes a new sandboxed Pipeline job with the name and Pipeline script you give; the folder must already exist.

  Try: “Create a Pipeline job called lint-check that runs npm run lint”

  Write · createPipeline

• Changes a build's display name or description

  Updates the name shown for a build and its description.

  Try: “Add the description 'hotfix for ticket 4521' to build 512”

  Write · updateBuild

• Checks whether your Jenkins is healthy and ready

  Reports the health and readiness of the Jenkins instance, beyond a simple up or down.

  Try: “Is our Jenkins healthy right now?”

  Read · getStatus

• Reads recent entries from the Jenkins system log

  Returns the newest system log entries, optionally from a named log recorder or above a minimum level. Needs system read permission.

  Try: “Show recent warnings from the Jenkins system log”

  Read · getSystemLog

• Lists the log recorders set up in Jenkins

  Returns the names of configured log recorders, for use when reading the system log. Needs system read permission.

  Try: “Which log recorders are configured?”

  Read · getLogRecorders

• Used by the assistant behind the scenes

  Shows which Jenkins user the assistant is acting as

  Returns details about the current user, useful to check the token is working.

  Try: “Which Jenkins user are you connected as?”

  Read · whoAmI

Watch out for

• It can run builds and Pipeline code

  It can trigger, rebuild and cancel builds, replay a Pipeline with a changed script and create Pipeline jobs. Use a Jenkins account limited to the jobs it needs. github.com

• It acts with your full Jenkins permissions

  Every tool runs as the user whose API token you give it, so an admin token gives the assistant admin reach. github.com

• Keep the plugin updated

  Older versions skipped permission checks on several tools. Update to the latest plugin version. jenkins.io

• Don't allow anonymous MCP access

  The allowUnauthenticatedMcp setting weakens CSRF protection. Leave it off on any controller people reach in a browser. github.com

• The token header is only encoded

  The header is your username and token in base64, which anyone can decode. Treat the config file like a password. github.com

Security advisories