Jenkins MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (default 3100) | 3100 |
| JENKINS_URL | Yes | Jenkins base URL | |
| MCP_HTTP_HOST | No | Bind host (default 127.0.0.1) | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP port (default 3100) | 3100 |
| JENKINS_USERNAME | Yes | Jenkins username | |
| JENKINS_API_TOKEN | Yes | Jenkins API token | |
| JENKINS_READ_ONLY | No | true disables jenkins_trigger_build | false |
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 |
|---|---|
| jenkins_whoamiA | Return the authenticated Jenkins user identity |
| jenkins_test_authA | Test Jenkins credential authentication and authorization (permissions) |
| jenkins_list_jobsB | List Jenkins jobs visible to the configured credentials |
| jenkins_get_jobB | Get details for a Jenkins job by name or folder path |
| jenkins_get_buildB | Get details for a specific build or the last build of a job |
| jenkins_get_build_logB | Get console log text for a Jenkins build |
| jenkins_get_queueA | List items currently in the Jenkins build queue |
| jenkins_get_nodesA | List Jenkins agents/nodes and their online status |
| jenkins_trigger_buildC | Trigger a Jenkins job build, optionally with parameters |
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 9 tools
Each tool targets a distinct aspect of Jenkins: builds, logs, jobs, nodes, queue, auth, and user identity. No two tools overlap in purpose.
All tools follow a consistent 'jenkins_verb_noun' snake_case pattern, making it predictable and easy to understand.
9 tools is well-scoped for a Jenkins MCP server, covering essential operations like listing, getting details, triggering builds, and checking status without overwhelming users.
Covers common read and trigger operations but lacks job creation, deletion, or parameter introspection. Minor gaps for full lifecycle management.