rundeck

This MCP server provides a bridge to manage Rundeck via AI, exposing a suite of tools for working with jobs, executions, projects, nodes, and system information. You can list, fetch details for, execute, and even predict outcomes for jobs; manage executions and retrieve their outputs; view projects and their information; and inspect node status and Rundeck system information. The server is run through a Node-based MCP host and relies on the Rundeck CLI tool for issuing commands to your Rundeck instance. Once configured, you can invoke the MCP endpoints via your client to perform typical Rundeck operations without manually typing CLI commands.

Prerequisites:

• Node.js v14 or higher
• Rundeck CLI tool installed and available at a known path

Steps:

1. Clone the repository and install dependencies:

git clone https://github.com/vanisoul/rundeck-mcp-server
cd rundeck-mcp-server
npm install

2. Build the project:

npm run build

3. Configure the MCP settings file (example provided in README):

{
  "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": []
    }
  }
}

4. Replace placeholders with your environment specifics:

• /path/to/rundeck-mcp-server/build/index.js -> absolute path to the built server entry
• /usr/bin/rd -> path to the Rundeck CLI tool
• http://your-rundeck-server:port/ -> your Rundeck server URL
• your-api-token -> API token for Rundeck

5. Restart your MCP host (e.g., VS Code plugin or Claude Desktop) to apply settings.
6. Use the MCP endpoints to interact with Rundeck through the provided tools.

Tips and common issues:

• Ensure the Rundeck CLI (rd) is correctly installed and accessible at the path specified in RUNDECK_CLI_PATH.
• The RUNDECK_BASE_URL must be reachable from the MCP server; verify network access and any required TLS settings.
• Generate and securely store your RUNDECK_API_TOKEN; avoid embedding secrets in logs or version control.
• If commands fail, check that the built index.js path is correct and that the MCP host has permissions to execute Node scripts.
• The MCP server relies on the Rundeck API; ensure API access and token permissions align with the operations you intend to perform (jobs, executions, projects, nodes).
• You can modify alwaysAllow to permit specific commands or users as needed for your environment.