render-deploy

A deployment assistant for Render's cloud platform that analyzes a codebase, generates configuration, and drives service creation, focusing on Git-backed services. It supports two methods: the Blueprint method, which produces a render.yaml Infrastructure-as-Code file for reproducible, version-controlled, multi-service setups, and Direct Creation, which provisions a single service instantly through Render MCP tools without a render.yaml. Prebuilt Docker image services are also possible (a Blueprint with runtime: image, which still requires a render.yaml in a Git repo), but image-backed services cannot be created through MCP and must go through the Dashboard or API.

A method-selection heuristic guides the choice: prefer Direct Creation when there is a single web app or static site with no separate worker or cron and no attached database or Key Value store; use a Blueprint whenever multiple services, datastores, cron jobs, background workers, private services, monorepos, or reproducible IaC are involved. If deployment intent is ambiguous (for example whether a database or workers are needed) it asks a short clarifying question but defaults to Blueprint for safety.

The skill enforces a prerequisites sequence — confirming a Git remote pushed to GitHub, GitLab, or Bitbucket, checking MCP tool availability via list_services(), optionally installing the Render CLI, and verifying authentication and the active workspace. It includes MCP setup instructions for Cursor, Claude Code, and Codex (adding the https://mcp.render.com/mcp server with a Render API key), a CLI fallback path using render whoami and render workspace commands, and provides Dashboard deeplinks to complete or monitor deployments.