Jenkins MCP

    1

    Diagnose failed builds, manage queues, and update Jenkins pipelines safely via MCP.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Jenkins MCP

    Example session with this skill installed

    Check why the 'auth-service/deploy-prod' job is stuck in the queue and see if there are any available nodes.

    • Read your context and instructions
    • Compiled the jenkins mcp

    I have inspected the Jenkins queue and node status for the requested job.

    Jenkins Queue and Node Audit

    CategoryDetailValue
    Target Jobauth-service/deploy-prodID: 442
    Queue StatusBlocked"Waiting for next available executor on 'production-slave'"
    Queue Item ID9821Entered queue at 2023-10-27 14:02:10 UTC
    Node: masterOnline0/2 executors free (Building: gateway-service #102, api-docs #45)
    Node: production-slaveOnline0/4 executors free (Building: auth-service #441, db-migration #12, heavy-test #9, cleanup #2)
    Node: build-agent-01OfflineDisconnected by admin: "Disk space low"

    Assessment
    The job is blocked because the required label production-slave is at full capacity (4/4 executors active). Additionally, one general-purpose build agent is offline, causing overflow contention on the remaining nodes. Confidence: High.

    Next steps

    1. Authorize bringing build-agent-01 back online if disk space has been cleared.
    2. Wait for auth-service #441 to complete (currently at 85% progress) to free an executor.
    3. Optionally cancel the cleanup #2 task if the production deployment has higher priority.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing Jenkins at scale through a chat interface often leads to blind retries, credential leaks, or destructive configuration overwrites. This skill provides a systematic approach for interacting with Jenkins via an MCP server, ensuring every action is grounded in live state rather than assumptions. It enforces a strict "read-before-write" workflow to prevent duplicate builds and accidental data loss.

    What it does

    • Root cause analysis parses build logs from byte offsets to identify the earliest causal failure in the pipeline.
    • Queue troubleshooting inspects specific queue items and node capacity to explain why a job is pending or blocked.
    • Safe build triggering handles parameterized jobs, monitors queue IDs, and tracks progress through to terminal status.
    • Infrastructure management allows for updating pipeline XML, offlining nodes, or stopping builds with explicit authorization gates.
    • State verification reads back job and node configurations after changes to confirm the intended effect was achieved.

    How it works

    1. Scope discovery uses list_jobs and get_job to resolve the exact folder-qualified path of the target project.
    2. Evidence collection retrieves build info, console logs, or queue state to build a diagnostic context.
    3. Change authorization prepares a reviewable diff or parameter set and waits for explicit user approval before execution.
    4. Action execution performs the trigger, update, or stop command using the verified ID or configuration XML.

    Frameworks & tools

    Specifically designed for the grglzrv/jenkins-mcp-server. It interacts with Jenkins pipelines, multibranch jobs, and node infrastructure via the Jenkins remote API.

    Why this beats prompting it yourself

    Generic prompts often guess build numbers or hallucinate pipeline syntax that breaks your XML configuration. This skill follows a specific sequence to correlate queue IDs with build numbers, ensuring you never lose track of a triggered job or overwrite a config without a backup.

    Use cases

    • Diagnose why a specific CI build failed and identify the exact failing stage.
    • Resolve "pending" status by checking node labels and executor availability.
    • Update Jenkinsfile pipeline scripts or job XML configurations safely.
    • Trigger deployments with specific parameters and follow the progress to completion.

    Known limitations

    Requires an active Jenkins MCP server connection and pre-configured Jenkins access. It cannot recover deleted jobs without external backups and does not support bypassing server-side permissions.

    Requires a connected Jenkins MCP server. Cannot recover deleted jobs without external backups. Access is limited to jobs visible to the provided credentials and server allowlist.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    Requires

    Jenkins MCP
    Python

    Permissions

    Network Access
    Read Files
    Listed26 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a bridge between your AI agent and the `grglzrv/jenkins-mcp-server`, providing a structured workflow for diagnosing failures, managing job queues, and safely updating pipeline configurations via the Jenkins remote API.

    Unlike generic prompts, this skill enforces a 'read-before-write' protocol, ensuring your AI agent verifies live job states and byte-offset logs before attempting any changes or triggers, which prevents duplicate builds and XML corruption.

    You will need an active Jenkins instance with remote API access enabled and the `grglzrv/jenkins-mcp-server` configured within your MCP-compatible environment (such as Claude Desktop or similar IDEs).

    Yes, the skill is designed to handle complex folder hierarchies by using `list_jobs` and `get_job` to resolve exact folder-qualified paths before execution.

    The skill includes a dedicated 'Change Authorization' step that generates a reviewable diff or parameter set, requiring your explicit approval before the AI can execute any destructive actions like stopping builds or updating XML.

    While the skill can update and verify job configurations, it cannot recover jobs that have already been deleted from the Jenkins server and does not bypass your existing server-side Jenkins permission settings.

    New in DevOps & Cloud