Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Jenkins CI/CD & Build Orchestration Pro

    1

    Connect your AI agent to enterprise Jenkins controllers. Manage 53 tools covering jobs, builds, queue inspection, build agent fleets, pipeline replay, and controller administration.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Jenkins CI/CD & Build Orchestration Pro

    Jenkins CI/CD & Build Orchestration Pro

    Example session with this skill installed

    Check the status of the 'frontend-build' job, find the last failed build, and show me the pipeline stages where it broke.

    • Read your context and instructions
    • Compiled the jenkins ci cd

    I have retrieved the status for the 'frontend-build' job and identified the latest failure in build #42. The pipeline failed during the 'Integration Tests' stage after running for 4 minutes.

    Build Failure Analysis: frontend-build #42

    StageStatusDurationError Summary
    CheckoutSUCCESS12sCode pulled from main branch
    Install DependenciesSUCCESS1m 45sAll npm packages resolved
    Unit TestsSUCCESS2m 10s450 tests passed
    Integration TestsFAILED4m 05sConnection timeout on port 8080
    Docker BuildSKIPPED0sStage not reached
    Push to RegistrySKIPPED0sStage not reached

    Build Metadata

    • Result: FAILURE
    • Timestamp: 2023-10-27 14:22:01
    • Trigger: Commit a1b2c3d by @developer_name
    • Log Snippet: [ERROR] Failed to connect to localhost/127.0.0.1:8080. Connection refused.

    Next steps

    1. Run jenkins_get_build_log(job_name="frontend-build", build_number=42, start_line=500) to see the full stack trace.
    2. Use jenkins_replay_pipeline to test a fix for the integration test timeout without a new commit.
    3. Check agent health with jenkins_get_node_info if this appears to be a network infrastructure issue.

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

    About this skill

    🚀 Production Workflows

    1. Parameterized Build Triggers & Queue Scheduling: Triggers matrix and parameterized jobs with validation, monitoring build queue position until execution.
    2. Console Log Failure Analysis: Scans thousands of console output lines, isolates stack traces, and pinpoints build failures in seconds.
    3. Flaky Stage Detection & Script Replay: Inspects Declarative Pipeline stage execution durations and replays pipelines with hotfixed scripts.
    4. Build Agent Fleet & Executor Health: Audits agent offline causes, inspects JVM executors, and safely takes nodes offline for patching.
    5. Release Promotion & Graceful Restart: Gating release builds, entering quiet down maintenance mode, and executing safe controller restarts.

    🛡️ Safety & Governance

    • Read-only autonomous log inspection, queue queries, and stage audits.
    • Confirmation-gated triggers, build aborts, node changes, and restarts.

    Launch via: uvx jenkins-mcp

    Requires JENKINS_URL and API token setup. Must run scripts/verify_env.py before first use. Destructive operations require explicit operator confirmation.

    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 16 days ago

    Requires

    Jenkins MCP
    uv (Python tool runner)
    Github MCP
    Artifact Registry MCP
    Observability MCP
    K8s MCP

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables
    Listed16 days ago

    What's inside

    Frequently Asked Questions

    This skill enables your AI agent to manage the entire Jenkins lifecycle—from triggering builds and triaging logs to managing build nodes and system plugins—without you ever needing to log into the web UI.

    The skill is compatible with any AI agent or IDE that supports the Model Context Protocol (MCP), such as Claude Desktop or various developer-focused AI tools.

    Yes, for security, the skill distinguishes between read-only inspection and administrative actions; destructive operations like deleting jobs or running Groovy scripts require an explicit operator confirmation.

    The server connects via the Jenkins Remote Access API and requires standard credentials (like an API token) configured via environment variables or a verification script.

    Absolutely. It is designed to work alongside other MCP servers, allowing you to create complex workflows like triggering a Jenkins build based on a GitHub PR or checking Kubernetes logs if a deployment fails.

    New in DevOps & Cloud