MCP-Jenkins

jenkins_get_node_status

Retrieve the status of a specific node in a Jenkins build by providing the application name, build number, and node ID. Use this tool to monitor and manage CI/CD pipeline node activities efficiently.

Instructions

Obtener el estado de un nodo específico de un build

Input Schema

Name	Required	Description
`app`	Yes	Nombre de la aplicación
`branch`	No	Rama de Git (por defecto: main)
`buildNumber`	Yes	Número del build
`nodeId`	Yes	ID del nodo

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "app": {
      "description": "Nombre de la aplicación",
      "type": "string"
    },
    "branch": {
      "description": "Rama de Git (por defecto: main)",
      "type": "string"
    },
    "buildNumber": {
      "description": "Número del build",
      "type": "number"
    },
    "nodeId": {
      "description": "ID del nodo",
      "type": "string"
    }
  },
  "required": [
    "app",
    "buildNumber",
    "nodeId"
  ],
  "type": "object"
}

This server cannot be installed

Other Tools from MCP-Jenkins

Related Tools

jenkins_get_build_steps
@gcorroto/mcp-jenkins
get_build_status
@hekmon8/Jenkins-server-mcp
get_build_status
@kjozsa/jenkins-mcp
jenkins_get_job_status
@gcorroto/mcp-jenkins
get_build_log
@hekmon8/Jenkins-server-mcp
get_hex_run_status
@franccesco/hex-mcp

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gcorroto/mcp-jenkins'

If you have feedback or need assistance with the MCP directory API, please join our Discord server