get_build_statusLABSCO SUMMARY
Read the failing build's console output where you are already asking about it.
Trigger, status, history and console log are the four things anyone opens Jenkins for, and the queue tools cover the case where nothing is running because something ahead of it is wedged. It authenticates as your own user, so its reach is exactly your account's.
What it is
A Jenkins bridge covering job listing and configuration, build triggering with parameters, build history and status, console output, queue monitoring, and navigation through Jenkins folders.
What you get
- Jobs listed, their configuration read, and their status monitored
- Builds triggered with parameters, and running builds stopped
- Build history, and the detail behind a single build
- Console output for a build, which is where a failure is actually explained
- The Jenkins build queue, including builds that are stuck in it
- Folder navigation, for instances organised into folders
Requirements
Node.js and a local build with npm install and npm run build, plus your Jenkins URL, a username and an API token set in the environment. The token is generated from Manage Jenkins then your user's Configure page, and is the recommended credential rather than a password.
Setup effort
Build from source — git clone https://github.com/ddang-jung/jenkins-mcp-server.git
USE CASES
01
Finding out why the build went red
Pull the build's status, then its console output, and let the assistant read the stack trace back to you with the failing step named, instead of you paging through a log in a browser tab.
02
Kicking off a parameterised build
Trigger the job with the parameters it expects, from the conversation where you decided to run it, and stop it again if you passed the wrong branch.
03
Working out whether the pipeline is stuck or just slow
Read the queue: a job that has not started because something is blocking it looks very different from one that is running slowly, and the queue tools separate the two.
04
Checking whether a failure is new
Read the job's build history and the detail of the last few runs, so you know whether this break arrived with today's commit or has been there for a week.
8 tools
Listed in project docs. Your client may show a different list.
trigger_buildget_build_loglist_jobsget_build_historystop_buildget_queueget_job_configBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- Node.js and npm
- JENKINS_URL in your environment
- JENKINS_USER in your environment
- JENKINS_TOKEN in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/ddang-jung/jenkins-mcp-server.git
cd jenkins-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jenkins": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JENKINS_MCP_SERVER>/build/index.js"
],
"env": {
"JENKINS_URL": "http://<YOUR_JENKINS_SERVER>:8080",
"JENKINS_USER": "<YOUR_JENKINS_USER>",
"JENKINS_TOKEN": "<YOUR_JENKINS_TOKEN>"
}
}
}
}
