Render Automation

1---
2name: render-automation
3description: "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas."
4requires:
5  mcp: [rube]
6---
7 
8# Render Automation via Rube MCP
9 
10Automate Render cloud platform operations through Composio's Render toolkit via Rube MCP.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17 
18## Setup
19 
20**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
21 
22 
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `render`
253. If connection is not ACTIVE, follow the returned auth link to complete Render authentication
264. Confirm connection status shows ACTIVE before running any workflows
27 
28## Core Workflows
29 
30### 1. List and Browse Services
31 
32**When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)
33 
34**Tool sequence**:
351. `RENDER_LIST_SERVICES` - List all services with optional filters [Required]
36 
37**Key parameters**:
38- `name`: Filter services by name substring
39- `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')
40- `limit`: Maximum results per page (default 20, max 100)
41- `cursor`: Pagination cursor from previous response
42 
43**Pitfalls**:
44- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'
45- Pagination uses cursor-based approach; follow `cursor` until absent
46- Name filter is substring-based, not exact match
47- Service IDs follow the format 'srv-xxxxxxxxxxxx'
48- Default limit is 20; set higher for comprehensive listing
49 
50### 2. Trigger Deployments
51 
52**When to use**: User wants to manually deploy or redeploy a service
53 
54**Tool sequence**:
551. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite]
562. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required]
573. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional]
58 
59**Key parameters**:
60- For TRIGGER_DEPLOY:
61  - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')
62  - `clearCache`: Set `true` to clear build cache before deploying
63- For RETRIEVE_DEPLOY:
64  - `serviceId`: Service ID
65  - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')
66 
67**Pitfalls**:
68- `serviceId` is required; resolve via LIST_SERVICES first
69- Service IDs start with 'srv-' prefix
70- Deploy IDs start with 'dep-' prefix
71- `clearCache: true` forces a clean build; takes longer but resolves cache-related issues
72- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status
73- Triggering a deploy while another is in progress may queue the new one
74 
75### 3. Monitor Deployment Status
76 
77**When to use**: User wants to check the progress or result of a deployment
78 
79**Tool sequence**:
801. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required]
81 
82**Key parameters**:
83- `serviceId`: Service ID (required)
84- `deployId`: Deployment ID (required)
85- Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit`
86 
87**Pitfalls**:
88- Both `serviceId` and `deployId` are required
89- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'
90- 'live' indicates successful deployment
91- 'build_failed' or 'update_failed' indicate deployment errors
92- Poll at reasonable intervals (10-30 seconds) to avoid rate limits
93 
94### 4. Manage Projects
95 
96**When to use**: User wants to list and organize Render projects
97 
98**Tool sequence**:
991. `RENDER_LIST_PROJECTS` - List all projects [Required]
100 
101**Key parameters**:
102- `limit`: Maximum results per page (max 100)
103- `cursor`: Pagination cursor from previous response
104 
105**Pitfalls**:
106- Projects group related services together
107- Pagination uses cursor-based approach
108- Project IDs are used for organizational purposes
109- Not all services may be assigned to a project
110 
111## Common Patterns
112 
113### ID Resolution
114 
115**Service name -> Service ID**:
116```
1171. Call RENDER_LIST_SERVICES with name=service_name
1182. Find service by name in results
1193. Extract id (format: 'srv-xxxxxxxxxxxx')
120```
121 
122**Deployment lookup**:
123```
1241. Store deployId from RENDER_TRIGGER_DEPLOY response
1252. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId
1263. Check status for completion
127```
128 
129### Deploy and Monitor Pattern
130 
131```
1321. RENDER_LIST_SERVICES -> find service by name -> get serviceId
1332. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId
1343. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId
1354. Check status: 'live' = success, 'build_failed'/'update_failed' = error
1365. Continue polling until terminal state reached
137```
138 
139### Pagination
140 
141- Use `cursor` from response for next page
142- Continue until `cursor` is absent or results are empty
143- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination
144- Set `limit` to max (100) for fewer pagination rounds
145 
146## Known Pitfalls
147 
148**Service IDs**:
149- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')
150- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')
151- Always resolve service names to IDs via LIST_SERVICES
152 
153**Service Types**:
154- Must use exact enum values when filtering
155- Available types: web_service, static_site, private_service, background_worker, cron_job
156- Different service types have different deployment behaviors
157 
158**Deployment Behavior**:
159- Deployments are asynchronous; always poll for completion
160- Clear cache deploys take longer but resolve stale cache issues
161- Failed deploys do not roll back automatically; the previous version stays live
162- Concurrent deploy triggers may be queued
163 
164**Rate Limits**:
165- Render API has rate limits
166- Avoid rapid polling; use 10-30 second intervals
167- Bulk operations should be throttled
168 
169**Response Parsing**:
170- Response data may be nested under `data` key
171- Timestamps use ISO 8601 format
172- Parse defensively with fallbacks for optional fields
173 
174## Quick Reference
175 
176| Task | Tool Slug | Key Params |
177|------|-----------|------------|
178| List services | RENDER_LIST_SERVICES | name, type, limit, cursor |
179| Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache |
180| Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId |
181| List projects | RENDER_LIST_PROJECTS | limit, cursor |
182