Rundeck MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNDECK_BASE_URL | Yes | Your Rundeck server URL, e.g., http://your-rundeck-server:port/ | |
| RUNDECK_CLI_PATH | Yes | Absolute path to the Rundeck CLI tool, e.g., /usr/bin/rd | |
| RUNDECK_API_TOKEN | Yes | Your Rundeck API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsB | 列出項目中的所有作業 |
| get_job_infoC | 獲取作業的詳細信息 |
| run_jobC | 執行作業 |
| list_executionsB | 列出項目中的執行 |
| get_execution_infoC | 獲取執行的詳細信息 |
| get_execution_outputC | 獲取執行的輸出 |
| list_projectsC | 列出所有項目 |
| get_project_infoC | 獲取項目的詳細信息 |
| list_nodesB | 列出項目中的節點 |
| get_system_infoB | 獲取 Rundeck 系統信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action (e.g., execution info vs. output, job info vs. list), with no overlap in purpose.
All tools follow a consistent 'verb_noun' snake_case pattern (e.g., get_execution_info, list_jobs, run_job), making them predictable.
With 10 tools, the surface covers key Rundeck operations (projects, jobs, executions, nodes, system info) without being excessive or sparse.
The set is strong for read and execute operations but lacks create/update/delete for jobs and projects, limiting full lifecycle coverage.