Pi + Render
Deploy and manage your Render apps from Pi.
Pi uses the Render Pi package to add Render skills and hosted MCP tools for services, deploys, logs, metrics, and databases.
Quick start
-
Install Pi and the Render package.
-
Restart Pi so it loads the package's skills and MCP adapter.
-
Connect with OAuth from a Pi session:
Approve the browser prompt. A single 401 before authentication is expected while the adapter initializes.
-
Verify the connection. Ask Pi to run
list_workspaces, choose a workspace if needed, then try "Deploy this project to Render."
MCP and authentication
pi install https://github.com/render-oss/render-pi-plugin~/.pi/agent/settings.jsonThe package owns its Render MCP connection, so Pi's generic /mcp setup, /mcp enable, and /mcp disable commands do not control it. For CI or headless Linux without an unlocked credential store, set RENDER_API_KEY before starting Pi instead of using OAuth.
See the MCP server docs for the full authentication reference and the Pi package for update and removal instructions.
Example prompts
Start with one of these prompts, then refine the plan with your agent.
Deploy this project to Render and explain the Blueprint before applying it.
Check the latest failed deploy, fix the cause, and verify the next deploy.
Create a Render Postgres database and connect it to this service with DATABASE_URL.
Summarize the health, recent deploys, and error logs for my Render services.
Common workflows
Deploy from the terminal
- Ask Pi to inspect the repository and propose a
render.yamlBlueprint. - Review the services, databases, and environment variables.
- Apply the plan, then check the first deploy.
Debug a failed deploy
- Ask Pi to fetch the latest failed deploy logs.
- Let it identify and fix the code, configuration, or environment issue.
- Verify the next deploy reaches a healthy state.
Add a database
- Ask Pi to create a Render Postgres database.
- Store its internal connection string as
DATABASE_URL. - Add migrations to the service's pre-deploy command.
Related agents
- Claude Code + RenderSet up Claude Code with Render MCP and Render skills for terminal-first deploys, debugging, and infrastructure changes.
- Claude Desktop + RenderConnect Claude Desktop to the Render MCP server to create services, query databases, and inspect logs and metrics from chat.
- Codex CLI + RenderConnect Codex CLI to Render so it can inspect services, read deploy logs, draft Blueprints, and manage deploy workflows from your terminal.
- Codex Desktop + RenderConnect Codex Desktop to Render with the Render plugin, skills, and OAuth-enabled MCP tools.
- Cursor + RenderAdd Render MCP and skills to Cursor so your editor agent can inspect services, update env vars, read logs, and manage deploy workflows in context.
- OpenCode + RenderConfigure OpenCode with the Render plugin, MCP, and skills for an open-source terminal workflow that can debug, create services, and deploy.