# Render

**Summary:** Connect the Render MCP server to Unless so your AI customer agent can check deploys and services on Render, each action permissioned and logged.

**In short:** Connect the Render MCP server so your Unless AI agent can check on deploys and services in Render.

**Published:** 2026-06-09

**Last updated:** 2026-08-10

## Context
Render is a cloud hosting platform for web services, static sites, background workers, and managed databases, deployed straight from a git push. Its MCP server puts that same infrastructure under AI control: checking whether a deploy succeeded, or restarting a service that has stalled.

With Unless, the Render MCP server plugs into Living Context. Checking a deploy or a service's health is something your agent handles alone; restarting or scaling that service touches something live, so it waits for the approval you configure, and either action lands in the audit trail.

### Key benefits
- __Status checks without the dashboard:__ Your agent can check a deploy or a service's health right inside the conversation.
- __Restarts stay a step you approve:__ Anything that touches a live service waits for the approval you've set, logged either way.

### How does it work?
Unless connects to the Render MCP server through Living Context. Deploy and service checks run on their own; restarting or scaling a service follows the approval you've configured, and every action against Render lands in the audit trail.

## Install instructions
Once at the [Integrations tab](https://unless.com/en/dashboard/data-management/integrations/kb/render "Unless dashboard integrations") of your Unless dashboard, you can select "Configure" for the Render integration. This will open a popup where you can connect the Render MCP server and set up the integration.
