Jenkins MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_JENKINS_URL | Yes | URL of the Jenkins server (e.g., https://pipeline.yourcompany.com) | |
| MCP_JENKINS_USER | No | Jenkins username for API token authentication | |
| MCP_JENKINS_API_TOKEN | No | Jenkins API token for authentication | |
| MCP_JENKINS_BEARER_TOKEN | No | Bearer token for authentication (alternative to user+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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jenkins_list_instancesA | List all configured Jenkins instances with their names and URLs |
| jenkins_list_jobsA | List all Jenkins jobs with their names and URLs |
| jenkins_search_jobsA | Search for Jenkins jobs by name (case-insensitive substring match) |
| jenkins_get_job_statusA | Get the status of the last build for a specific job |
| jenkins_get_job_parametersA | Get the parameter definitions for a parameterised Jenkins job — names, types, defaults, and choices |
| jenkins_get_build_statusB | Get detailed status of a specific build number for a job |
| jenkins_get_recent_buildsA | Get recent builds for a job with their status and metadata |
| jenkins_get_console_logA | Get console log output from a build. Returns both a snippet and full log. |
| jenkins_trigger_buildB | Trigger a new build for a job, optionally with parameters |
| jenkins_list_artifactsA | List all artifacts produced by a specific build |
| jenkins_get_artifactA | Download a specific artifact from a build (returns base64-encoded content) |
| jenkins_stop_buildA | Stop/abort a running build |
| jenkins_delete_buildB | Delete a specific build |
| jenkins_get_test_resultsA | Get test results for a build (pass/fail counts, test suites) |
| jenkins_get_build_changesB | Get Git commits/changes for a build |
| jenkins_get_pipeline_stagesA | Get pipeline stages and their status for a build |
| jenkins_replay_buildA | Replay/rerun a pipeline build, optionally with a modified pipeline script |
| jenkins_get_queueB | Get the current build queue showing pending builds |
| jenkins_cancel_queueA | Cancel a queued build by queue ID |
| jenkins_enable_jobB | Enable a disabled job |
| jenkins_disable_jobB | Disable a job to prevent it from running |
| jenkins_delete_jobA | Permanently delete a job (WARNING: cannot be undone) |
| jenkins_get_job_configA | Get job configuration XML |
| jenkins_list_nodesA | List all Jenkins nodes/agents and their status |
| jenkins_get_system_infoA | Get Jenkins system information |
| jenkins_get_versionC | Get Jenkins version |
| jenkins_get_pluginsA | List all installed Jenkins plugins |
| jenkins_create_jobB | Create a new Jenkins job from an XML configuration |
| jenkins_update_job_configA | Update an existing job's XML configuration |
| jenkins_rename_jobB | Rename a Jenkins job |
| jenkins_copy_jobB | Copy/duplicate a Jenkins job under a new name |
| jenkins_get_nodeA | Get detailed information about a specific Jenkins node/agent |
| jenkins_toggle_node_offlineB | Toggle a Jenkins node/agent between online and offline |
| jenkins_list_viewsA | List all Jenkins views with their jobs |
| jenkins_get_viewB | Get details and job list for a specific Jenkins view |
| jenkins_quiet_downA | Put Jenkins into quiet mode — no new builds will start until cancelled (requires confirm: true) |
| jenkins_cancel_quiet_downB | Cancel Jenkins quiet mode and resume accepting new builds |
| jenkins_safe_restartA | Safely restart Jenkins — waits for running builds to finish before restarting (requires confirm: true) |
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 38 tools
Each tool targets a distinct Jenkins resource or action (e.g., jobs, builds, nodes, views), with clear boundaries. Overlap like get_build_status vs get_job_status is resolved by explicit parameter differences.
All tools follow the consistent pattern 'jenkins_verb_noun' (e.g., jenkins_create_job, jenkins_list_jobs), with no mixing of conventions or ambiguous verbs.
38 tools is significantly above the typical well-scoped range of 3-15. While Jenkins is complex and many tools are justified, the count feels heavy and could overwhelm agents.
Core operations for jobs and builds are covered, but notable gaps exist: no create/delete for nodes or views, and missing build triggers. This leaves some workflows incomplete.