count_failed_jobs
Count how many Jenkins jobs currently have their last build in FAILURE state.
LABSCO SUMMARY
Status, trigger, log — the loop you repeat when CI is red.
Everything here is scoped to one job path at a time, so it fits the moment a build breaks: ask what happened, read the console output, fix, and trigger again with the same parameters. It does not browse Jenkins for you — you need to know the job path — and it does not manage jobs, credentials or nodes.
What it is
A small MCP server over a Jenkins CI/CD server. It covers the three things you actually do when a build is in question: find out whether it passed, kick off a new one with the parameters you want, and read the log when it did not.
What you get
- The status of a build, by job path and build number, defaulting to the latest build —
get_build_status - A new build triggered on a job, with build parameters passed as key-value pairs such as a branch and a build type —
trigger_build - The console output of a build, so a failure can be read and explained rather than opened in a browser —
get_build_log
Requirements
A Jenkins server and an API token for a user on it: JENKINS_URL, JENKINS_USER and JENKINS_TOKEN. The npm package name is jenkins-server (0.1.0) and it is marked private, so build from a clone with npm install and npm run build, then point your client at the built index.js. The token can start builds, so give it an account with the job permissions you intend and no more.
Setup effort
One command plus a key — npx -y github:hekmon8/Jenkins-server-mcp, then supply credentials
USE CASES
01
Finding out why the build went red
Check the status of the last build, then pull its console output and have the model point at the failing step instead of scrolling the log yourself.
02
Re-running a build on a different branch
Trigger the job with the branch and build type as parameters, without opening the Jenkins interface to fill in the form.
03
Confirming a fix landed
Trigger the build after pushing, then check its status and read the log if it fails again.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_jenkins_user
Create a new Jenkins user in the internal user database. Requires admin permissions.
get_build_log
Get the console output of a Jenkins build
get_build_status
Get the status of a Jenkins build
get_failed_build_log
Get the console output of the last failed build for a given Jenkins job.
list_recent_failed_jobs
List Jenkins jobs whose most recent build failed, sorted by most recent failure time.
trigger_build
Trigger a new Jenkins build
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. Only get_build_status, trigger_build and get_build_log are documented; create_jenkins_user is an undocumented write that creates Jenkins accounts.
Requires
- npx on PATH
- JENKINS_TOKEN in your environment
- JENKINS_USER in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Build from source
TERMINAL
git clone https://github.com/hekmon8/jenkins-server-mcp.git
cd jenkins-server-mcp
npm install
npm run buildnpx
TERMINAL
npx -y github:hekmon8/Jenkins-server-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jenkins-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JENKINS_SERVER_MCP>/build/index.js"
],
"env": {
"JENKINS_URL": "<YOUR_JENKINS_URL>",
"JENKINS_USER": "<YOUR_JENKINS_USER>",
"JENKINS_TOKEN": "<YOUR_JENKINS_TOKEN>"
}
}
}
}
