Skip to main content
Glama
Rundeck MCP Server

Rundeck MCP Server

by vanisoul

Rundeck MCP Server

This is a Model Context Protocol (MCP) server for interacting with the Rundeck CLI. It provides a set of tools that allow you to perform Rundeck operations with AI without directly interacting with the command line.

Features

  • Jobs Management: List, get information, execute, and predict

  • Executions Management: List, get information, get output, and track

  • Projects Management: List and get information

  • Nodes and System Information: List nodes and get system information

Related MCP server: rundeck-mcp-server

Installation

Prerequisites

  • Node.js (v14 or higher)

  • Rundeck CLI tool

Steps

  1. Clone this repository:

git clone https://github.com/vanisoul/rundeck-mcp-server
cd rundeck-mcp-server
  1. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Configure the MCP settings file:

Add the following configuration to your MCP settings file. The location of the settings file depends on your environment:

{
  "mcpServers": {
    "rundeck": {
      "command": "node",
      "args": ["/path/to/rundeck-mcp-server/build/index.js"],
      "env": {
        "RUNDECK_CLI_PATH": "/usr/bin/rd",
        "RUNDECK_BASE_URL": "http://your-rundeck-server:port/",
        "RUNDECK_API_TOKEN": "your-api-token"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Make sure to replace the following values:

  • /path/to/rundeck-mcp-server/build/index.js: The absolute path to the built index.js file

  • /usr/bin/rd: The absolute path to the Rundeck CLI tool

  • http://your-rundeck-server:port/: Your Rundeck server URL

  • your-api-token: Your Rundeck API token

  1. Restart VS Code or Claude Desktop for the settings to take effect.

How to Install Rundeck CLI

Troubleshooting

If you encounter issues, check the following:

  1. Ensure the Rundeck CLI tool is available and working properly

  2. Make sure the RUNDECK_CLI_PATH environment variable points to the correct Rundeck CLI tool path

  3. Ensure the RUNDECK_BASE_URL and RUNDECK_API_TOKEN environment variables are set correctly

  4. Check that the MCP settings file is configured correctly

License

MIT

Available Tools

10 tools
get_execution_infoC

獲取執行的詳細信息

Inputs: id (required).

get_execution_outputC

獲取執行的輸出

Inputs: id (required), tail.

get_job_infoC

獲取作業的詳細信息

Inputs: id (required).

get_project_infoC

獲取項目的詳細信息

Inputs: project (required).

get_system_infoB

獲取 Rundeck 系統信息

Inputs: no named parameters.

list_executionsB

列出項目中的執行

Inputs: project (required), max.

list_jobsB

列出項目中的所有作業

Inputs: project (required), format.

list_nodesB

列出項目中的節點

Inputs: project (required), filter.

list_projectsC

列出所有項目

Inputs: format.

run_jobC

執行作業

Inputs: id (required), options.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action (e.g., execution info vs. output, job info vs. list), with no overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent 'verb_noun' snake_case pattern (e.g., get_execution_info, list_jobs, run_job), making them predictable.

    Tool Count5/5

    With 10 tools, the surface covers key Rundeck operations (projects, jobs, executions, nodes, system info) without being excessive or sparse.

    Completeness3/5

    The set is strong for read and execute operations but lacks create/update/delete for jobs and projects, limiting full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers