jenkins_list_jobsLABSCO SUMMARY
The build is triggered and diagnosed in one place.
The log and the artifact sit on the same connection as the trigger, so 'run it and tell me why it failed' does not become three browser tabs. Prefixed tool names let a prod and a staging Jenkins be connected at the same time.
What it is
A Go MCP server over the Jenkins REST API. It covers jobs, builds, the queue, logs, artifacts and views, authenticates with a username and API token over TLS, and retries transient failures with exponential backoff.
What you get
- Jobs and views listed, and one job's detail read
- A build triggered, running builds watched, and a build stopped
- A build's status read, and its console log retrieved
- The queue read, a queue item inspected, and a queued item cancelled
- A build's artifacts listed and downloaded
- Tool names prefixed through JENKINS_TOOL_PREFIX, so several Jenkins instances can be connected at once
Requirements
A Jenkins instance plus a username and API token — JENKINS_URL, JENKINS_USERNAME and JENKINS_API_TOKEN, or the same values in config.yaml. A custom CA certificate, timeouts and retry counts are configurable; building from source needs Go 1.23.6 or later.
Setup effort
Run a container — pull the image and point your client at it
USE CASES
01
Kicking off a build without opening Jenkins
Find the job, trigger it, and watch the running builds.
02
Working out why the build went red
Read the build's status, then pull the console log.
03
Clearing a jammed queue
Read the queue, inspect the item that is stuck, and cancel it.
04
Getting the binary the build produced
List a build's artifacts and download the one you want.
05
Stopping a run that is going nowhere
Stop the build instead of waiting out the timeout.
06
Finding your way around someone else's Jenkins
List the views, then read the detail on the jobs behind them.
18 tools
Listed in project docs. Your client may show a different list.
jenkins_get_jobjenkins_trigger_buildjenkins_get_buildjenkins_get_build_logjenkins_get_running_buildsjenkins_stop_buildjenkins_list_artifactsjenkins_get_artifactjenkins_get_queuejenkins_get_queue_itemjenkins_cancel_queue_itemjenkins_list_viewsjenkins_get_viewjenkins_create_viewjenkins_server_healthjenkins_list_nodesjenkins_get_pipeline_scriptBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- docker on PATH
- JENKINS_API_TOKEN in your environment
- JENKINS_USERNAME in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jenkins": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"JENKINS_URL=<YOUR_JENKINS_URL>",
"-e",
"JENKINS_USERNAME=<YOUR_JENKINS_USERNAME>",
"-e",
"JENKINS_API_TOKEN=<YOUR_JENKINS_API_TOKEN>",
"-e",
"JENKINS_TOOL_PREFIX=prod",
"ghcr.io/nithishnithi/jenkins-mcp-server:v1.0.5"
]
}
}
}<YOUR_JENKINS_URL> is the URL of your Jenkins instance, and <YOUR_JENKINS_API_TOKEN> is a Jenkins API token (in Jenkins: your name, top right → Configure → API Token → Add new Token). JENKINS_TOOL_PREFIX=prod renames every tool with a prod_ prefix (prod_jenkins_list_jobs); it is optional and only needed to run several Jenkins servers side by side, so drop that -e pair if you connect one.
