Render CLI for managing services, deploys, logs, databases, workflows, and blueprint validation.
$brew install render
Agent Compatibility
JSON Output
Agent Skill
MCP Support
AI Analysis
Render CLI is Render's command-line client for operating services, datastores, and workflow services on the platform. It combines a default Bubble Tea TUI with non-interactive commands for deploys, logs, jobs, database access, blueprint validation, and some early-access storage workflows.
What It Enables
- List services, datastores, projects, workspaces, deploys, jobs, environments, workflow versions, tasks, and task runs from the shell.
- Trigger deploys, restarts, one-off jobs, workflow releases, and workflow task runs, then wait for completion and inspect logs or returned resource state.
- Open
psql,pgcli,redis-cli, or SSH sessions, validaterender.yamlblueprints before deploys, and upload or fetch objects in Render's early-access object storage.
Agent Fit
- Many read and write commands support
--output json|yaml|text,--confirm, and API-key auth, which makes inspect-change-verify loops workable in CI and agent scripts. - Structured responses plus
--waitflows for deploys and workflow releases make it practical to trigger an action, poll, and branch on success or failure without scraping the dashboard. - The automation surface is mixed rather than perfect: the CLI defaults to a fullscreen TUI, non-TTY mode falls back to text unless you set output explicitly, and session-oriented commands like SSH stay human-interactive.
Caveats
- Useful unattended usage usually requires explicit
--output jsonorRENDER_OUTPUT=json; auto mode does not default to JSON. - You still need Render auth and workspace context, and some capabilities are intentionally terminal-session workflows rather than machine-first APIs.