Integration

Rundeck integration

Rundeck runbook automation API for a self-hosted server: list projects and their jobs, read a job definition and its options, run a job with parameters, follow the resulting execution through its status, per step state and log output, abort a running execution, search execution history, run adhoc commands on project nodes and read server information. Point the credential at your own Rundeck host and authenticate with an API token.

Connect Rundeck How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Rundeck use cases

validating a new Rundeck credential
triggering a deployment job from a workflow
checking whether the last run of a job succeeded
reporting every failed execution of the last week
stopping a runaway deployment job from a workflow
finding the identifier of a job before triggering it
inspecting the node source configuration of a project
polling until a job started by a workflow has finished
discovering which projects exist before listing their jobs
fetching the log of a failed job to explain what went wrong

What you can do with Rundeck

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.

Execution, 5 operations

abort_executionAbort executionGETRequests that a running Rundeck execution be aborted.
get_executionGet executionGETReturns the status of one Rundeck execution.
list_job_executionsList job executionsGETLists the past executions of a Rundeck job.
list_running_executionsList running executionsGETLists the Rundeck executions currently running in a project.
query_executionsQuery executionsGETSearches the Rundeck execution history of a project.

Job, 4 operations

get_job_definitionGet job definitionGETExports the full Rundeck job definition with its steps and options.
get_job_infoGet job infoGETReturns the metadata of a Rundeck job including its average run time.
list_jobsList jobsGETLists the Rundeck jobs of a project with their schedule state.
run_jobRun jobPOSTStarts a Rundeck job and returns the execution that was created.

Project, 2 operations

get_projectGet projectGETReturns one Rundeck project with its configuration properties.
list_projectsList projectsGETLists the Rundeck projects available on the server.

Command, 1 operation

run_adhoc_commandRun adhoc commandPOSTRuns an adhoc shell command on the nodes of a Rundeck project.

Execution output, 1 operation

get_execution_outputGet execution outputGETReturns the log output of a Rundeck execution and the offset to continue from.

Execution state, 1 operation

get_execution_stateGet execution stateGETReturns the per step and per node state of a Rundeck execution.

Node, 1 operation

list_project_nodesList project nodesGETLists the nodes a Rundeck project can target.

System info, 1 operation

get_system_infoGet system infoGETReturns the Rundeck server version, uptime and execution mode.

Use Rundeck from Claude Code, Cursor or Codex

Connect Rundeck in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Rundeck 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 Rundeck

Create your workspace
Sign up free. Nothing to install.
Connect Rundeck once
Add your Rundeck 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.

Rundeck integration FAQ

What can you do with the Rundeck integration?

LiveContext exposes 16 operations on Rundeck, covering execution, job, project and command. Common uses include validating a new Rundeck credential, triggering a deployment job from a workflow and checking whether the last run of a job succeeded.