Kiwi for Render
Have the agent on a Kiwi step trigger a Render deploy, filter the service's logs and read its metrics, through Render's MCP server.
- Your agent works in Render through its own connection. Kiwi does not call Render and never holds its credentials.
- A workflow skill can list Render among the tools it requires. When you supply your agent's available tools to a skill check and Render is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Render, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Render connection, with
report_configuration. - The agent submits links to its work in Render as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Render
- Create web services, cron jobs, Postgres databases and Key Value instances.
- Update a service's environment variables.
- Trigger a deploy and list a service's deploy history.
- Filter a service's logs and read its metrics.
- Run read-only SQL against a Render Postgres database.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Render
Add the Render MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.render.com/mcpExample skill
Publish instructions like these as a workflow skill that lists Render among its required tools.
Read the Render service name from the step's inputs. Trigger a deploy of the staging service, then list its deploy history to confirm that the deploy finished. Filter the service's logs for errors since the deploy. Submit the deploy ID and the error lines as the step's outputs. Production deploys wait for the run's Owner. If the deploy fails, report a blocker.