| name | rundeck-mcp-connector |
| description | MCP connector for Rundeck operations automation – enables AI-powered job creation, node management, and runbook automation through Claude |
| license | Apache 2.0 |
| tags | ["cloud","automation","mcp","rundeck","operations"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Rundeck MCP Connector
Overview
This skill enables Claude to interact with Rundeck through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Rundeck's REST API, allowing natural language control of Rundeck operations, intelligent automation, and AI-powered assistance for Rundeck workflows.
When to Use This Skill
- Job definition and scheduling via natural language
- Node filtering and command execution
- Workflow step design and error handling
- Key storage and credential management
- Execution history analysis and reporting
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Rundeck │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Rundeck operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/41/job, /api/41/execution, /api/41/project, /api/41/system, /api/41/storage
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "rundeck-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Rundeck resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/41/job`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"rundeck-mcp-connector": {
"command": "node",
"args": ["path/to/rundeck-mcp-connector/index.js"],
"env": {
"RUNDECK_API_KEY": "your-api-key",
"RUNDECK_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Rundeck API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Rundeck API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a maintenance job that runs database backup, clears logs, and restarts services on weekend nights"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
