jenkins_build_manager
Gestionar builds de Jenkins: listar, consultar, iniciar, esperar, detener con confirmación, reconstruir, replay, logs y artifacts
LABSCO SUMMARY
Handling pending input steps is what makes this usable on real pipelines, where a build waiting on approval is indistinguishable from a build that is stuck.
Jenkins pipelines with manual gates are common and they break most integrations: the build is neither running nor finished, and a poller reports it as in progress forever. Finding pending actions and submitting an approval turns that from a dead end into a step the agent can complete or escalate. Line-level coverage is the other detail worth having — a coverage percentage tells you there is a problem and covered lines for a specific file tells you where. Tool descriptions are in Spanish.
What it is
A Jenkins client covering jobs and builds, pipeline monitoring including input steps, and code coverage retrieval at three levels of detail.
What you get
- Jobs started against a specific branch, stopped, and inspected — with jenkins_get_git_branches listing what is available to build.
- jenkins_wait_for_build blocks until a build finishes or detects a pause, which is what makes a build step in an agent workflow synchronous.
- Input steps handled properly: jenkins_get_pending_actions finds a build waiting on approval, and jenkins_submit_input_action approves or rejects it.
- jenkins_pipeline_monitor covers stages, nodes and pending inputs together, and per-build tools read step and node status individually.
- Coverage at three granularities — the report, the file paths that have coverage, and the covered lines within a specific file.
- jenkins_job_manager and jenkins_build_manager consolidate the list, read, create and update operations rather than spreading them across many tools.
Requirements
A reachable Jenkins instance with credentials for it.
Setup effort
One command plus credentials — npm install -g @grec0/mcp-jenkins, then supply credentials
USE CASES
01
Building a branch and waiting for the result
See which branches are available, start the job against one, and block until the build finishes rather than polling.
02
Unblocking a pipeline waiting on approval
Find the build sitting on a pending input step and approve or reject it, instead of reading it as stuck.
03
Finding out which stage failed
Read the build's step status and the node status underneath it, rather than the overall result.
04
Checking what the tests actually covered
Read the coverage report, then the files with coverage, then the covered lines in the file you care about.
05
Managing the jobs themselves
List, read, create and update job and pipeline configuration through the consolidated managers rather than tool by tool.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
jenkins_get_build_steps
Obtener el estado de los steps de un build específico
jenkins_get_coverage_lines
Obtener líneas de cobertura de un archivo específico
jenkins_get_coverage_paths
Obtener todos los paths de archivos con cobertura
jenkins_get_coverage_report
Obtener reporte de cobertura de código de un build
jenkins_get_git_branches
Obtener las ramas de Git disponibles para un job
jenkins_get_job_status
Obtener el estado de un job específico de Jenkins
jenkins_get_node_status
Obtener el estado de un nodo específico de un build
jenkins_get_pending_actions
Obtener las acciones pendientes de input de un build
jenkins_job_manager
Gestionar jobs y pipelines de Jenkins: listar, leer, crear, actualizar config, borrar, habilitar, deshabilitar y ramas Git
jenkins_pipeline_monitor
Monitorear pipelines Jenkins: stages, nodos, inputs pendientes y envío de acciones de input
jenkins_start_job
Iniciar un job de Jenkins con una rama específica
jenkins_stop_job
Detener un job de Jenkins en ejecución
jenkins_submit_input_action
Enviar una acción de input a Jenkins (aprobar/rechazar)
jenkins_wait_for_build
Esperar de forma bloqueante a que termine un build de Jenkins o detectar pausas manuales con input pendiente para poder aprobarlas desde MCP
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. jenkins_job_manager and jenkins_build_manager each bundle nine actions, including delete, update_config, stop and replay; destructive ones require confirmName or confirmBuild. Stage, coverage and git-branch tools need Jenkins plugins such as pipeline-rest-api and git-parameter.
Requires
- npx on PATH
- Node.js 18
- JENKINS_PASSWORD in your environment
- JENKINS_USERNAME in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @grec0/mcp-jenkinsMCP Clients
VS Code — npx
VS CODE — NPX · JSON
{
"servers": {
"jenkins": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"--package",
"@grec0/mcp-jenkins@latest",
"mcp-jenkins"
],
"env": {
"JENKINS_URL": "<YOUR_JENKINS_URL>/jenkins",
"JENKINS_USERNAME": "<YOUR_JENKINS_USERNAME>",
"JENKINS_PASSWORD": "<YOUR_JENKINS_PASSWORD>"
}
}
}
}Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"jenkins": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"--package",
"@grec0/mcp-jenkins@latest",
"mcp-jenkins"
],
"env": {
"JENKINS_URL": "<YOUR_JENKINS_URL>/jenkins",
"JENKINS_USERNAME": "<YOUR_JENKINS_USERNAME>",
"JENKINS_PASSWORD": "<YOUR_JENKINS_PASSWORD>"
}
}
}
}Any MCP client — global binary
ANY MCP CLIENT — GLOBAL BINARY · JSON
{
"mcpServers": {
"jenkins": {
"type": "stdio",
"command": "mcp-jenkins",
"env": {
"JENKINS_URL": "<YOUR_JENKINS_URL>/jenkins",
"JENKINS_USERNAME": "<YOUR_JENKINS_USERNAME>",
"JENKINS_PASSWORD": "<YOUR_JENKINS_PASSWORD>"
}
}
}
}
