Rundeck Mcp Server
Drive Rundeck jobs, executions, projects, nodes, and system settings from your AI agent through 50 MCP tools instead of clicking the UI.
Overview
rundeck-mcp-server is an MCP server for the Operate phase that exposes 50 tools to manage Rundeck jobs, executions, projects, nodes, and system settings.
What is this MCP server?
- 50 MCP tools covering jobs, executions, projects, nodes, and system APIs
- npm package rundeck-mcp-server v1.0.3 with stdio transport
- Env-configured RUNDECK_URL and RUNDECK_API_TOKEN (API v41 default)
- Configurable RUNDECK_TIMEOUT (default 30000 ms)
- [object Object]
What problem does it solve?
Switching between Rundeck’s UI and your agent breaks flow when you need to rerun jobs or inspect executions during incidents.
Who is it for?
Builders who already use Rundeck for ops automation and want MCP-driven job and execution management.
Skip if: Greenfield projects with no Rundeck deployment or anyone who only needs generic SSH/cron without Rundeck.
What do I get? / Deliverables
After install, your agent can query and control Rundeck via MCP using your API token and server URL.
- MCP tools mapped to Rundeck jobs, executions, projects, nodes, and system
- Agent-driven rerun and inspection of executions
- Configurable API version and request timeout
Recommended MCP Servers
Journey fit
How it compares
Rundeck-specific ops MCP with 50 tools, not a generic cloud provisioning skill.
Common Questions / FAQ
Who is rundeck-mcp-server for?
Developers and solo operators who run Rundeck and want their coding agent to manage jobs, executions, projects, and nodes over the Rundeck API.
When should I use rundeck-mcp-server?
Use it in Operate when you need to trigger runbooks, check execution status, or maintain Rundeck projects and nodes from an MCP session.
How do I add rundeck-mcp-server to my agent?
Install rundeck-mcp-server from npm, set RUNDECK_URL and RUNDECK_API_TOKEN (and optional RUNDECK_API_VERSION, RUNDECK_TIMEOUT), add stdio MCP config, then restart your agent.