Render Automation via Rube MCP
Automate Render cloud platform operations through Composio's Render toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Render connection via
RUBE_MANAGE_CONNECTIONS with toolkit render
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit render
- If connection is not ACTIVE, follow the returned auth link to complete Render authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Browse Services
When to use: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)
Tool sequence:
RENDER_LIST_SERVICES - List all services with optional filters [Required]
Key parameters:
name: Filter services by name substring
type: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')
limit: Maximum results per page (default 20, max 100)
cursor: Pagination cursor from previous response
Pitfalls:
- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'
- Pagination uses cursor-based approach; follow
cursor until absent
- Name filter is substring-based, not exact match
- Service IDs follow the format 'srv-xxxxxxxxxxxx'
- Default limit is 20; set higher for comprehensive listing
2. Trigger Deployments
When to use: User wants to manually deploy or redeploy a service
Tool sequence:
RENDER_LIST_SERVICES - Find the service to deploy [Prerequisite]
RENDER_TRIGGER_DEPLOY - Trigger a new deployment [Required]
RENDER_RETRIEVE_DEPLOY - Monitor deployment progress [Optional]
Key parameters:
- For TRIGGER_DEPLOY:
serviceId: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')
clearCache: Set true to clear build cache before deploying
- For RETRIEVE_DEPLOY:
serviceId: Service ID
deployId: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')
Pitfalls:
serviceId is required; resolve via LIST_SERVICES first
- Service IDs start with 'srv-' prefix
- Deploy IDs start with 'dep-' prefix
clearCache: true forces a clean build; takes longer but resolves cache-related issues
- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status
- Triggering a deploy while another is in progress may queue the new one
3. Monitor Deployment Status
When to use: User wants to check the progress or result of a deployment
Tool sequence:
RENDER_RETRIEVE_DEPLOY - Get deployment details and status [Required]
Key parameters:
serviceId: Service ID (required)
deployId: Deployment ID (required)
- Response includes
status, createdAt, updatedAt, finishedAt, commit
Pitfalls:
- Both
serviceId and deployId are required
- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'
- 'live' indicates successful deployment
- 'build_failed' or 'update_failed' indicate deployment errors
- Poll at reasonable intervals (10-30 seconds) to avoid rate limits
4. Manage Projects
When to use: User wants to list and organize Render projects
Tool sequence:
RENDER_LIST_PROJECTS - List all projects [Required]
Key parameters:
limit: Maximum results per page (max 100)
cursor: Pagination cursor from previous response
Pitfalls:
- Projects group related services together
- Pagination uses cursor-based approach
- Project IDs are used for organizational purposes
- Not all services may be assigned to a project
Common Patterns
ID Resolution
Service name -> Service ID:
1. Call RENDER_LIST_SERVICES with name=service_name
2. Find service by name in results
3. Extract id (format: 'srv-xxxxxxxxxxxx')
Deployment lookup:
1. Store deployId from RENDER_TRIGGER_DEPLOY response
2. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId
3. Check status for completion
Deploy and Monitor Pattern
1. RENDER_LIST_SERVICES -> find service by name -> get serviceId
2. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId
3. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId
4. Check status: 'live' = success, 'build_failed'/'update_failed' = error
5. Continue polling until terminal state reached
Pagination
- Use
cursor from response for next page
- Continue until
cursor is absent or results are empty
- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination
- Set
limit to max (100) for fewer pagination rounds
Known Pitfalls
Service IDs:
- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')
- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')
- Always resolve service names to IDs via LIST_SERVICES
Service Types:
- Must use exact enum values when filtering
- Available types: web_service, static_site, private_service, background_worker, cron_job
- Different service types have different deployment behaviors
Deployment Behavior:
- Deployments are asynchronous; always poll for completion
- Clear cache deploys take longer but resolve stale cache issues
- Failed deploys do not roll back automatically; the previous version stays live
- Concurrent deploy triggers may be queued
Rate Limits:
- Render API has rate limits
- Avoid rapid polling; use 10-30 second intervals
- Bulk operations should be throttled
Response Parsing:
- Response data may be nested under
data key
- Timestamps use ISO 8601 format
- Parse defensively with fallbacks for optional fields
Quick Reference
| Task |
Tool Slug |
Key Params |
| List services |
RENDER_LIST_SERVICES |
name, type, limit, cursor |
| Trigger deploy |
RENDER_TRIGGER_DEPLOY |
serviceId, clearCache |
| Get deploy status |
RENDER_RETRIEVE_DEPLOY |
serviceId, deployId |
| List projects |
RENDER_LIST_PROJECTS |
limit, cursor |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: render-automation3description: "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas."4risk: unknown5source: community6date_added: "2026-02-27"7metadata:8 source: https://skillmd.com/skills/phoroth/render-automation9---1011# Render Automation via Rube MCP1213Automate Render cloud platform operations through Composio's Render toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**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.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `render`283. If connection is not ACTIVE, follow the returned auth link to complete Render authentication294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. List and Browse Services3435**When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)3637**Tool sequence**:381. `RENDER_LIST_SERVICES` - List all services with optional filters [Required]3940**Key parameters**:41- `name`: Filter services by name substring42- `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')43- `limit`: Maximum results per page (default 20, max 100)44- `cursor`: Pagination cursor from previous response4546**Pitfalls**:47- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'48- Pagination uses cursor-based approach; follow `cursor` until absent49- Name filter is substring-based, not exact match50- Service IDs follow the format 'srv-xxxxxxxxxxxx'51- Default limit is 20; set higher for comprehensive listing5253### 2. Trigger Deployments5455**When to use**: User wants to manually deploy or redeploy a service5657**Tool sequence**:581. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite]592. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required]603. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional]6162**Key parameters**:63- For TRIGGER_DEPLOY:64 - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')65 - `clearCache`: Set `true` to clear build cache before deploying66- For RETRIEVE_DEPLOY:67 - `serviceId`: Service ID68 - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')6970**Pitfalls**:71- `serviceId` is required; resolve via LIST_SERVICES first72- Service IDs start with 'srv-' prefix73- Deploy IDs start with 'dep-' prefix74- `clearCache: true` forces a clean build; takes longer but resolves cache-related issues75- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status76- Triggering a deploy while another is in progress may queue the new one7778### 3. Monitor Deployment Status7980**When to use**: User wants to check the progress or result of a deployment8182**Tool sequence**:831. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required]8485**Key parameters**:86- `serviceId`: Service ID (required)87- `deployId`: Deployment ID (required)88- Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit`8990**Pitfalls**:91- Both `serviceId` and `deployId` are required92- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'93- 'live' indicates successful deployment94- 'build_failed' or 'update_failed' indicate deployment errors95- Poll at reasonable intervals (10-30 seconds) to avoid rate limits9697### 4. Manage Projects9899**When to use**: User wants to list and organize Render projects100101**Tool sequence**:1021. `RENDER_LIST_PROJECTS` - List all projects [Required]103104**Key parameters**:105- `limit`: Maximum results per page (max 100)106- `cursor`: Pagination cursor from previous response107108**Pitfalls**:109- Projects group related services together110- Pagination uses cursor-based approach111- Project IDs are used for organizational purposes112- Not all services may be assigned to a project113114## Common Patterns115116### ID Resolution117118**Service name -> Service ID**:119```1201. Call RENDER_LIST_SERVICES with name=service_name1212. Find service by name in results1223. Extract id (format: 'srv-xxxxxxxxxxxx')123```124125**Deployment lookup**:126```1271. Store deployId from RENDER_TRIGGER_DEPLOY response1282. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId1293. Check status for completion130```131132### Deploy and Monitor Pattern133134```1351. RENDER_LIST_SERVICES -> find service by name -> get serviceId1362. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId1373. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId1384. Check status: 'live' = success, 'build_failed'/'update_failed' = error1395. Continue polling until terminal state reached140```141142### Pagination143144- Use `cursor` from response for next page145- Continue until `cursor` is absent or results are empty146- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination147- Set `limit` to max (100) for fewer pagination rounds148149## Known Pitfalls150151**Service IDs**:152- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')153- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')154- Always resolve service names to IDs via LIST_SERVICES155156**Service Types**:157- Must use exact enum values when filtering158- Available types: web_service, static_site, private_service, background_worker, cron_job159- Different service types have different deployment behaviors160161**Deployment Behavior**:162- Deployments are asynchronous; always poll for completion163- Clear cache deploys take longer but resolve stale cache issues164- Failed deploys do not roll back automatically; the previous version stays live165- Concurrent deploy triggers may be queued166167**Rate Limits**:168- Render API has rate limits169- Avoid rapid polling; use 10-30 second intervals170- Bulk operations should be throttled171172**Response Parsing**:173- Response data may be nested under `data` key174- Timestamps use ISO 8601 format175- Parse defensively with fallbacks for optional fields176177## Quick Reference178179| Task | Tool Slug | Key Params |180|------|-----------|------------|181| List services | RENDER_LIST_SERVICES | name, type, limit, cursor |182| Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache |183| Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId |184| List projects | RENDER_LIST_PROJECTS | limit, cursor |185186## When to Use187This skill is applicable to execute the workflow or actions described in the overview.188189## Limitations190- Use this skill only when the task clearly matches the scope described above.191- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.192- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.