Jenkins MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JENKINS_TOKEN | No | Jenkins authentication token | |
| SHLAB_JENKINS_TOKEN | No | SHLAB Jenkins token | |
| JENKINS_MCP_LOG_LEVEL | No | Log level for debugging (e.g., DEBUG) | |
| PROD_BLSM_JENKINS_TOKEN | No | Production Jenkins token | |
| JENKINS_MCP_SCENARIOS_FILE | No | Path to custom scenarios file |
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 |
|---|---|
| get_server_namesA | Get the list of all available Jenkins server names. |
| get_scenario_listA | Get all available application scenarios - the preferred entry point for deployment tasks. |
| search_jobs_by_scenarioB | Get the specified Jenkins job directly by scenario. |
| search_jobsA | Search Jenkins jobs on the specified server. |
| get_job_parametersB | Get the parameter definitions of a Jenkins job. |
| trigger_buildA | Trigger Jenkins job build. |
| get_build_statusC | Get the Jenkins build status for the specified build_number. |
| stop_buildB | Stop Jenkins build. |
| get_build_logC | Get Jenkins build log. |
| validate_jenkins_configB | Validate the integrity of Jenkins configuration. |
| create_or_update_job_from_jenkinsfileA | Create or update a Jenkins job based on a Jenkinsfile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scenario_selection_prompt | Generate a prompt for scenario selection to help the user choose the appropriate application scenario. |
| scenario_guidance_prompt | Generate a guidance prompt based on the user's selected scenario. |
| get_scenario_config | Get the complete configuration information for the specified scenario. |
| job_description_prompt | Generate a brief description prompt for a Jenkins job. |
| build_result_summary_prompt | Generate a Jenkins build result interpretation prompt. |
| build_log_analysis_prompt | Generate a Jenkins build log analysis prompt. |
| trigger_job_prompt | Generate a prompt for triggering a job. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but some potential overlap exists. For example, search_jobs and search_jobs_by_scenario both search for jobs, though the latter is scenario-specific. Additionally, get_build_log and get_build_status both retrieve build information, but their distinct focuses (log vs. status) help differentiate them. Overall, the tools are well-separated with clear boundaries.
The naming follows a consistent snake_case pattern with clear verb_noun structures, such as get_build_log and trigger_build. However, there are minor deviations like create_or_update_job_from_jenkinsfile, which is more verbose and includes a preposition, and validate_jenkins_config, which uses a noun_verb_noun pattern. These inconsistencies are minor and do not significantly hinder readability.
With 11 tools, the count is well-suited for a Jenkins MCP server. It covers essential operations like job management (create/update, search), build control (trigger, stop, get status/log), and configuration (validate, get parameters). The tools are focused and each serves a clear purpose without being overly broad or sparse.
The toolset provides strong coverage for core Jenkins workflows, including job creation, building, monitoring, and searching. However, there are minor gaps, such as the lack of tools for deleting jobs or managing Jenkins plugins/users. The inclusion of scenario-based deployment tools adds a layer of abstraction that enhances usability but doesn't fill all potential gaps in the Jenkins API surface.