Integration

Jenkins integration

Jenkins CI/CD automation server REST API for managing jobs, builds, pipelines, nodes, and queues. Trigger builds, monitor build status, manage credentials, and control Jenkins infrastructure.

Connect Jenkins How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Jenkins.Built from the 26 Jenkins tools below, on the connection you add once.

Common Jenkins use cases

Clean up deprecated CI/CD jobs
Cancel a build queued by mistake
List all dashboard views in Jenkins
Check Jenkins server status and mode
Get build history for a specific job
Trigger a CI build after a code push
Export a job configuration for backup
Check if a specific build agent is online
List all CI/CD jobs in a Jenkins instance
Programmatically create new CI/CD pipelines

What you can do with Jenkins

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Job, 9 operations

copy_jobCopy jobPOSTCreate a new Jenkins job by copying the configuration of an existing job
create_jobCreate jobPOSTCreate a new Jenkins job by posting its XML configuration
delete_jobDelete jobPOSTPermanently delete a Jenkins job and all its build history
disable_jobDisable jobPOSTDisable a Jenkins job to prevent it from being triggered or built
enable_jobEnable jobPOSTEnable a previously disabled Jenkins job so it can be built again
get_job_configGet job configGETRetrieve the raw XML configuration of a Jenkins job
get_job_infoGet job infoGETRetrieve detailed information about a specific Jenkins job including build history
list_jobsList jobsGETList all jobs on the Jenkins server with their names, URLs, and build status
update_job_configUpdate job configPOSTUpdate a Jenkins job by posting a modified XML configuration

Build, 7 operations

build_jobBuild jobPOSTTrigger a new build for a parameterless Jenkins job
build_with_parametersBuild with parametersPOSTTrigger a new parameterized build with custom parameter values
delete_buildDelete buildPOSTPermanently delete a specific build record from the job's build history
get_build_console_outputGet build console outputGETRetrieve the plain text console log output of a specific build
get_build_infoGet build infoGETRetrieve detailed information about a specific build including result, duration, and artifacts
get_last_buildGet last buildGETRetrieve information about the most recent build of a Jenkins job
stop_buildStop buildPOSTAbort a currently running Jenkins build

Server, 4 operations

get_crumbGet crumbGETRetrieve the CSRF crumb token needed to authenticate POST requests
get_server_infoGet server infoGETRetrieve Jenkins server information including version, mode, and available jobs
restart_jenkinsRestart jenkinsPOSTImmediately restart the Jenkins server, killing all running builds
safe_restartSafe restartPOSTRestart Jenkins safely by waiting for all running builds to complete first

Node, 2 operations

get_node_infoGet node infoGETRetrieve detailed information about a specific Jenkins node including executor and monitor data
list_nodesList nodesGETList all Jenkins nodes (master and agents) with their status and executor information

Queue, 2 operations

cancel_queued_itemCancel queued itemPOSTCancel a build that is waiting in the Jenkins build queue
get_build_queueGet build queueGETRetrieve the list of items currently waiting in the Jenkins build queue

View, 2 operations

get_viewGet viewGETRetrieve a specific Jenkins view including its jobs and configuration
list_viewsList viewsGETList all Jenkins views with their names and URLs

Use Jenkins from Claude Code, Cursor or Codex

Connect Jenkins in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Jenkins operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Jenkins

Create your workspace
Sign up free. Nothing to install.
Connect Jenkins once
Add your Jenkins connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Jenkins integration FAQ

What can you do with the Jenkins integration?

LiveContext exposes 26 operations on Jenkins, covering job, build, server and node. Common uses include Clean up deprecated CI/CD jobs, Cancel a build queued by mistake and List all dashboard views in Jenkins.