MCP-Jenkins
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JENKINS_URL | Yes | The URL of your Jenkins server. | |
| JENKINS_PASSWORD | Yes | Your Jenkins API token or password. | |
| JENKINS_USERNAME | Yes | Your Jenkins username. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jenkins_get_job_statusC | Obtener el estado de un job específico de Jenkins |
| jenkins_start_jobC | Iniciar un job de Jenkins con una rama específica |
| jenkins_stop_jobC | Detener un job de Jenkins en ejecución |
| jenkins_get_build_stepsC | Obtener el estado de los steps de un build específico |
| jenkins_get_node_statusC | Obtener el estado de un nodo específico de un build |
| jenkins_get_pending_actionsC | Obtener las acciones pendientes de input de un build |
| jenkins_submit_input_actionC | Enviar una acción de input a Jenkins (aprobar/rechazar) |
| jenkins_get_coverage_reportC | Obtener reporte de cobertura de código de un build |
| jenkins_get_coverage_linesC | Obtener líneas de cobertura de un archivo específico |
| jenkins_get_coverage_pathsC | Obtener todos los paths de archivos con cobertura |
| jenkins_get_git_branchesC | Obtener las ramas de Git disponibles para un job |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose targeting specific Jenkins resources and actions, with no overlapping functionality. For example, jenkins_get_coverage_lines and jenkins_get_coverage_paths serve different coverage-related queries, while jenkins_start_job and jenkins_stop_job handle opposite lifecycle actions.
All tools follow a perfectly consistent 'jenkins_verb_noun' naming pattern using snake_case throughout. The structure is predictable with the server prefix, action verb, and resource noun clearly separated, making it easy for agents to parse and understand.
With 11 tools, this server is well-scoped for Jenkins CI/CD operations, covering job management, build monitoring, coverage reporting, and input handling. Each tool earns its place without redundancy, providing a comprehensive yet manageable interface for typical Jenkins automation tasks.
The toolset covers core Jenkins workflows including job control (start/stop/status), build monitoring (steps/node/actions), and code coverage reporting. Minor gaps exist, such as missing job configuration management or artifact retrieval tools, but agents can accomplish most essential CI/CD operations with this surface.