jankins
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JENKINS_URL | Yes | Jenkins server URL | |
| JENKINS_USER | Yes | Jenkins username | |
| JENKINS_API_TOKEN | Yes | Jenkins API token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsA | List Jenkins jobs with optional prefix filtering and pagination |
| get_jobB | Get detailed information about a specific Jenkins job |
| trigger_buildC | Trigger a new build for a Jenkins job with optional parameters |
| enable_jobB | Enable a Jenkins job to allow builds |
| disable_jobB | Disable a Jenkins job to prevent builds |
| get_buildC | Get information about a specific build or the last build |
| get_build_changesB | Get SCM changes (commits) for a build |
| get_build_artifactsC | Get artifacts produced by a build |
| get_build_logA | Get build log with smart truncation and filtering. Returns summary by default, full text on request. |
| search_logB | Search build log for pattern and return matching lines with context |
| tail_log_liveA | Get log chunk for live tailing (poll repeatedly with next_byte for streaming effect) |
| get_job_scmB | Get SCM configuration for a job |
| get_build_scmA | Get SCM information (git commit, branch, etc.) for a build |
| whoamiA | Get current authenticated user information |
| get_statusA | Get Jenkins server status and queue depth |
| summarize_queueC | Get compact summary of Jenkins build queue |
| triage_failureC | Analyze a failed build and provide root cause hypotheses and next steps |
| compare_runsA | Compare two builds to identify differences in duration, stages, and results |
| get_pipeline_graphA | Get pipeline execution graph with stages, parallel branches, and timing (requires Blue Ocean plugin) |
| analyze_build_logB | Analyze build logs with build tool-specific parsers (Maven, Gradle, NPM) for detailed error analysis |
| retry_flaky_buildB | Retry a flaky build multiple times until it succeeds or max retries reached |
| get_test_reportB | Get test results summary from a build (JUnit, pytest, etc.) |
| get_failed_testsC | Get list of failed tests from a build with error details |
| compare_test_resultsB | Compare test results between two builds to identify new failures and regressions |
| detect_flaky_testsB | Identify flaky tests (inconsistent pass/fail) across recent builds |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_failure | Investigate a failing pipeline step with root cause analysis |
| tail_errors | Tail only warnings and errors for the last run |
| compare_builds | Compare two builds to identify differences |
| check_job_health | Check overall health and stability of a job |
| trigger_with_params | Trigger a parameterized build with guidance |
| search_logs | Search build logs for a specific pattern or error |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools have distinct purposes (job management, build inspection, test analysis, pipeline, queue, user info). Some overlap exists between log-related tools (analyze_build_log vs search_log vs tail_log_live) but descriptions clarify their unique functions. SCM tools (get_build_scm vs get_build_changes) are also clearly separated.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_build_log, compare_runs, disable_job). No mixed conventions or inconsistent naming styles are observed.
25 tools is slightly above the ideal range (3-15) but is reasonable for a comprehensive Jenkins integration covering jobs, builds, tests, pipelines, queue, and user info. The count is earned given the breadth of functionality.
The tool set covers major CI/CD workflows: job management (list, get, enable/disable, trigger), build inspection (logs, artifacts, SCM, comparisons), test analysis, pipeline visualization, queue, and user info. Missing: job creation/deletion, build cancellation, and configuration editing, but core troubleshooting and monitoring are well-represented.