render-deploy

SKILL.md

Deploy applications to Render with Git-backed services or prebuilt Docker images via Blueprint or direct creation.

Supports two deployment methods: Blueprint (Infrastructure-as-Code via render.yaml) for multi-service apps, and Direct Creation (MCP tools) for single services

Analyzes codebases to determine runtime, build/start commands, environment variables, and required datastores (databases, Redis, cron jobs)

Generates render.yaml configurations with automatic service type selection (web, worker, cron, static, pserv) and validates syntax before deployment

Provides Dashboard deeplinks for Git-backed deployments and includes post-deploy verification via logs, metrics, and health checks

Requires Git repository pushed to GitHub, GitLab, or Bitbucket; offers MCP setup guidance for Cursor, Claude Code, and Codex

Deploy to Render

Render supports Git-backed services and prebuilt Docker image services.

This skill covers Git-backed flows:

Blueprint Method - Generate render.yaml for Infrastructure-as-Code deployments

Direct Creation - Create services instantly via MCP tools

Blueprints can also run a prebuilt Docker image by using runtime: image, but the render.yaml still must live in a Git repo.

If there is no Git remote, stop and ask the user to either:

Create/push a Git remote (can be minimal if only the Blueprint is needed), or

Use the Render Dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services).

Prerequisites

When sandboxing blocks the deployment network calls, rerun with sandbox_permissions=require_escalated.

The deployment might take a few minutes. Use appropriate timeout values.