jenkins-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JENKINS_TIMEOUT | No | HTTP timeout in seconds | 30 |
| JENKINS_BASE_URL | Yes | Base URL of the Jenkins controller | http://localhost:8080 |
| JENKINS_USERNAME | Yes | Jenkins user for HTTP basic auth | |
| JENKINS_API_TOKEN | Yes | Jenkins API token (create in user settings) | |
| JENKINS_VERIFY_SSL | No | Verify TLS certificates | true |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsA | List Jenkins jobs. Optionally scoped to a folder path like |
| get_jobA | Return full job metadata for |
| trigger_buildA | Trigger a Jenkins build. Uses |
| get_buildB | Return detailed information about a specific build. |
| get_build_logA | Return the plain-text console log for a build. |
| stop_buildC | Request cancellation of an in-progress build. |
| list_buildsA | Return up to |
| list_queueA | Return all items currently in the Jenkins build queue. |
| cancel_queue_itemA | Cancel a queued build by its queue item id. |
| list_nodesA | Return all known Jenkins nodes/agents (including the built-in controller). |
| get_plugin_listA | Return all installed Jenkins plugins with metadata (depth=1). |
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 11 tools
Each tool targets a distinct resource and action: jobs, builds, queue, nodes, plugins. Even the build-related tools (get_build, list_builds, get_build_log) are clearly separated by their specific purpose.
All tool names follow a consistent verb_noun pattern (list_, get_, trigger_, stop_, cancel_), with clear and predictable naming throughout.
With 11 tools, the set is well-scoped for a Jenkins MCP server, covering job management, build inspection, queue control, nodes, and plugins without unnecessary bloat.
The core lifecycle of inspecting and triggering builds is well covered. The main gap is lack of job creation/configuration tools, but those are often outside the typical read/trigger scope of such a server.