host-mcp-jenkins
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | HTTP server port (only with transport http) | 3000 |
| LOG_LEVEL | No | Log level: debug, info, warn, error | info |
| JENKINS_URL | Yes | Jenkins base URL | |
| JENKINS_USER | Yes | Jenkins username | |
| MCP_TRANSPORT | No | Transport type: stdio or http | stdio |
| JENKINS_TIMEOUT | No | HTTP request timeout in milliseconds | 30000 |
| JENKINS_INSECURE | No | Skip TLS certificate verification (set to 'true') | false |
| JENKINS_API_TOKEN | Yes | Jenkins API token | |
| JENKINS_MAX_RETRIES | No | Max retries for transient errors | 3 |
| JENKINS_RETRY_DELAY | No | Base delay in ms for exponential backoff | 1000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getJobA | Get a Jenkins job by its full path |
| getJobsA | Get a paginated list of Jenkins jobs, sorted by name |
| getBuildA | Get a specific build or the last build of a Jenkins job |
| triggerBuildC | Trigger a build for a Jenkins job |
| updateBuildA | Update build display name and/or description |
| whoAmIA | Get information about the currently authenticated user |
| getStatusA | Checks the health and readiness status of a Jenkins instance |
| getQueueItemA | Get the queue item details by its ID |
| getBuildLogB | Retrieves some log lines with pagination for a specific build or the last build |
| getProgressiveBuildLogA | Retrieves build log output incrementally using Jenkins progressive text API. Pass the returned nextByteOffset as the start parameter in subsequent calls to get only new output. Ideal for tailing logs of running builds without re-fetching the entire log. |
| searchBuildLogB | Search for log lines matching a pattern in a specific build or the last build |
| getJobScmB | Retrieves SCM configurations of a Jenkins job |
| getBuildScmB | Retrieves SCM configurations of a Jenkins build |
| getBuildChangeSetsB | Retrieves change log sets of a Jenkins build |
| findJobsWithScmUrlA | Get a paginated list of Jenkins jobs that use the specified git SCM URL |
| getTestResultsB | Retrieves the test results associated to a Jenkins build |
| getFlakyFailuresA | Retrieves the flaky failures associated to a Jenkins build if any found |
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 17 tools
Each tool targets a distinct aspect of Jenkins (jobs, builds, logs, SCM, queue, status, authentication). Even similar tools like getBuildLog and getProgressiveBuildLog serve clearly different use cases (full paginated vs incremental tailing).
Tool names consistently follow a verb_noun pattern with camelCase, using clear verbs like get, find, search, trigger, update, whoAmI. No mixing of styles or inconsistent naming conventions.
17 tools cover a broad but focused set of Jenkins operations. While slightly above the ideal range, each tool earns its place for a comprehensive CI/CD assistant. Could be trimmed slightly, but still well-scoped.
Covers job discovery, build details, logs, SCM, triggering, and updates. Notable gaps include listing builds for a job, aborting builds, and viewing build parameters, which agents may need but are absent.