Connect Jenkins to Claude Desktop, Claude Code, Cursor, or any MCP-compatible AI agent: fetch console logs, inspect pipeline stages, parse JUnit and
Connect Jenkins to Claude Desktop, Claude Code, Cursor, or any MCP-compatible AI agent: fetch console logs, inspect pipeline stages, parse JUnit and Ginkgo test
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| health_check | Validate the server's setup: Jenkins reachability and version, authenticated user, CSRF crumb issuer, Pipeline/JUnit plugin presence, online/offline node counts |
| get_plugin_versions | List installed Jenkins plugins with versions, pinned flag, and pending-update flag. Optional name_filter (RE2) and include_inactive. 403 degrades to a clear hin |
| whoami_can | Probe a job for the configured token's effective Read / Build / Cancel / Configure permissions via read-only GET requests. Useful up-front to avoid a 403 on a t |
| list_jobs | Enumerate jobs and folders under a path (or root). Optional recursion and case-insensitive RE2 name filter; capped at 500 entries. |
| list_branches | Enumerate the branches of a WorkflowMultiBranchProject with per-branch last-build number, result, duration, and timestamp. Optional name_filter (RE2) and health |
| get_console_log | Tail the build's /consoleText. Defaults to last 500 lines; pass tail_lines: -1 for the full log. |
| get_console_log_path | Force-cache the full log for a completed build and return its on-disk path so the agent can Read/Grep/Bash it natively. |
| search_console_log | RE2 regex search over the console log with line-number-aware context windows. |
| tail_running_build | Capped, offset-tracked tail of an in-flight build's console via Jenkins' progressiveText. Echo Next since_byte back to paginate. Never writes to the on-disk cac |
| get_build_info | Pretty-printed build summary: result, duration, parameters, change set. |
| get_build_environment | Three sections for a build: Cause (trigger reason verbatim), Parameters (masked secrets surfaced as (masked)), and Injected Env Vars via EnvInject. Optional RE2 |
| get_scm_context | Per-commit history for one build: commit id, author, timestamp, message subject, and each commit's touched paths with A/M/D edit codes. Pipeline change sets are |
| last_green_build | Report the most recent successful build of a job. Returns number, finish time (UTC), and URL — the start point for bisect-from-green. |
| changes_since_last_green | Union the commits across every completed build since the job's last green. Walks previousCompletedBuild, dedupes by commitId, supports path_filter and max_commi |
| compare_builds | Diff two builds of the same job across result, duration, parameters, SCM commits, pipeline stages, and JUnit tests. The agent answers "what changed between A an |
| get_pipeline_stages | List Declarative/Scripted Pipeline stages via /wfapi/describe with status and duration. |
| get_stage_log | Fetch a single pipeline stage's log via /execution/node/ /wfapi/log. |
| get_pipeline_script | Return the Jenkinsfile a specific build actually ran. Tries the Replay plugin first (build-pinned), falls back to config.xml (job-level — provenance surfaced). |
| get_test_report | Structured JUnit results from /testReport/api/json, with failed cases and head+tail of stack traces. |
| get_flaky_candidates | Rank flaky tests across the latest N completed builds of one job by counting pass↔fail flips. Returns a sorted table of test name, flip count, pass/fail tallies |
| get_test_history | Per-build trend of a single test across the last N completed builds — the follow-up to get_flaky_candidates once a suspect is known. Timeline (build , result, s |
| find_test_by_name | Locate which job runs a test whose full name contains a substring. Walks list_jobs(recursive) under folder_path, fans out per-job probes against lastCompletedBu |
| find_recent_failures | Survey failed builds across the jobs under folder_path within a lookback window. Per-job probe of the last 5 builds; filters by since (24h default; supports Nd) |
| list_pr_builds | List all builds for a PR on a WorkflowMultiBranchProject. Probes the common PR branch naming conventions in parallel (PR-N, pull/N/head, change-N, pr/N) and ren |
| get_ginkgo_failure_summary | Parse Ginkgo's Summarizing N Failure block and surface the first [ERROR] tagged with each spec name. |
| list_nodes | List Jenkins agents/nodes with status, executor counts, labels, and monitor summaries. |
| get_node | Per-node detail: status, per-executor idle state, labels, full monitor data. |
| list_queue | List pending Jenkins queue items with the block reason for each. |
| cancel_queue_item | Drop a pending queue item by id. Mutating; suppressed when JENKINS_MCP_READONLY is set. |
| trigger_build | Queue a build, optionally with parameters; can block until the build is assigned a number. Mutating. |
| stop_build | Abort a running build. Mutating. |
{
"mcpServers": {
"jenkins": {
"command": "/usr/local/bin/jenkins-mcp",
"env": {
"JENKINS_URL": "https://jenkins.example.com",
"JENKINS_USER": "your-username",
"JENKINS_API_TOKEN": "YOUR_JENKINS_API_TOKEN"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| JENKINS_URL | Declared in the maintainer’s client configuration. | Check documentation |
| JENKINS_USER | Declared in the maintainer’s client configuration. | Check documentation |
| JENKINS_API_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Enables AI assistants to securely interact with Azure DevOps through a standardized protocol.
Finds the GitHub Actions steps that stop running on 2026-09-23, with the version to move to
Real-time GitHub Actions observability: DORA Metrics, Cost Analysis, CI/CD Health dashboards.
aica(AI Code Analyzer) reviews your code using AI. Supports CLI and GitHub Actions.
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform.