Rundeck MCP Server
Related Servers
Alternatives to Rundeck MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to manage Rundeck operations including jobs, executions, projects, nodes, system management, key storage, webhooks, and ACL policies via natural language.5035 npm1Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI-driven interaction with Rundeck via CLI for managing jobs, executions, projects, and nodes without direct command line usage.1035 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Rundeck automation platform, including project and job management, execution, and system monitoring through the MCP protocol.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Jenkins CI jobs, including triggering and stopping builds, retrieving job details, and fetching build logs.-
- AlicenseNot gradedqualityDmaintenanceMCP server enabling AI assistants to manage Rundeck projects, jobs, and executions through a standardized interface.MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to access Jenkins job data, trigger builds, and manage Jenkins tasks through a standardized interface.5-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get_execution retrieves metadata, get_execution_output fetches logs, get_job shows job details, list_executions filters executions, and list_jobs lists jobs. The separation between execution-focused and job-focused tools is well-defined, preventing agent confusion.
All tools follow a consistent verb_noun naming pattern (get_execution, get_execution_output, get_job, list_executions, list_jobs) with clear verbs (get, list) and specific nouns. There are no deviations in style or convention throughout the set.
Five tools is reasonable for a Rundeck server, covering core read operations for jobs and executions. However, the absence of tools for creating, updating, or running jobs makes the set feel slightly thin for full workflow automation, though it's well-scoped for monitoring and querying.
The tool set is severely incomplete for a Rundeck domain, which typically involves job execution and management. There are no tools to run jobs, create/update/delete jobs or executions, or manage projects—major gaps that will cause agent failures in automating Rundeck workflows beyond passive observation.