jenkins-server-mcp
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_USER | Yes | Jenkins username for authentication | |
| JENKINS_TOKEN | Yes | Jenkins API token for authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_build_statusB | Get the status of a Jenkins build |
| list_all_jobsA | List all Jenkins jobs with their name, URL, and last build status. |
| list_recent_failed_jobsB | List Jenkins jobs whose most recent build failed, sorted by most recent failure time. |
| count_failed_jobsA | Count how many Jenkins jobs currently have their last build in FAILURE state. |
| get_failed_build_logB | Get the console output of the last failed build for a given Jenkins job. |
| create_jenkins_userA | Create a new Jenkins user in the internal user database. Requires admin permissions. |
| trigger_buildB | Trigger a new Jenkins build |
| get_build_logC | Get the console output of a Jenkins build |
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 8 tools
Most tools have distinct purposes, but 'get_build_log' and 'get_failed_build_log' could cause minor confusion, and 'count_failed_jobs' and 'list_recent_failed_jobs' overlap in domain though differ in output.
All tool names use snake_case with verb_noun pattern (e.g., trigger_build, list_all_jobs). The naming is largely consistent, though 'get_failed_build_log' is a longer variant of 'get_build_log'.
With 8 tools, the set is well-scoped for a Jenkins monitoring and triggering server, covering essential operations without excess.
The server covers basic monitoring (status, logs, failed jobs) and build triggering, but lacks job creation, deletion, configuration update, or parameterized build support, leaving notable gaps.