Connect Render

Agents inspect Render services, deploys, logs and metrics and query Render Postgres; connects with a Render API key.

Once Render is connected, an agent can list your workspaces and services, walk through recent deploys and their logs, read CPU, memory and response-time metrics, trigger a deploy or update environment variables when you ask, and run read-only SQL against a Render Postgres database.

Before you start

A Render account. API keys belong to your user and carry your access in every workspace you are a member of, including deploys and environment variables.
You must be a workspace owner or admin in woble. Only owners and admins can connect integrations.

Connect it

Open Marketplace, Integrations tab, find Render and press Add.
In another tab, open the Render Dashboard, then Account Settings, API Keys. The direct link is dashboard.render.com/u/settings?add-api-key, which opens the create form for you.
Press Create API Key, give it a name such as "woble", and copy the key. It starts with rnd_ and Render shows it only once.
Back in woble, paste it into the Render API key field and press Connect. The card says Connected and the agent panel lists the new tools: list_workspaces, select_workspace, list_services, list_deploys, list_logs, trigger_deploy, query_render_postgres and more.

Or ask an agent

Type "@ruby connect Render" in any chat. The same card appears there with the same field. Only owners or admins can complete it.

Try it

"@atlas in the Acme workspace on Render, which services deployed in the last 24 hours and did any fail?"
"@atlas query the orders database on Render: how many orders were placed yesterday?"

Agents select a workspace first, diagnose with services, deploys and logs before acting, and confirm before triggering a deploy or touching environment variables. SQL through the connection is read-only.

If it does not connect

"Unauthorized" or an empty workspace list: the key was pasted with a missing character or extra space, or it was revoked in Render. Press Test connection in Marketplace, Connected; if it fails, Remove, create a fresh key and add it again.
A workspace is missing: the Render user who made the key is not a member of it.
The MCP server cannot change scaling, create image-backed services or edit IP allowlists. Those are Render limits, not connection problems.

Disconnect

Marketplace, Connected, Remove. The stored key is deleted and agents lose the Render tools immediately. Also revoke the key in Render under Account Settings, API Keys, so it cannot be used anywhere else.