Render

Render

This connector works with Render through the Render API (https://api.render.com/v1): workspaces and projects, services, deploys, one-off jobs, logs, metrics, events, custom domains, the names of environment variables, and Render Postgres and Key Value instances. It can deploy, roll back, cancel deploys, restart, suspend and resume services and run one-off jobs after you confirm.

Setup (about 2 minutes)

1. In the Render Dashboard open Account Settings > API Keys (https://dashboard.render.com/u/settings#api-keys) and click Create API Key.
2. Name it, copy it (it starts with rnd_) and paste it into RENDER_API_KEY. It is sent as Authorization: Bearer <key> to api.render.com only.
3. Check the setup with render_get_current_user, then render_list_workspaces.

A Render API key has your full rights in every workspace you belong to; there are no read-only keys. Share the MCP server only with people allowed to deploy, and switch off the write tools for a read-only setup.

How to work

1. render_list_workspaces gives the workspace id (ownerId), needed for logs. render_list_projects shows how services are grouped.
2. render_list_services gives service ids (srv-..., crn-... for cron jobs); render_get_service the details.
3. Deploys: render_list_deploys, render_get_deploy, and render_list_events for what happened to a service.
4. Logs: render_list_logs with owner_id and the service id as resource; filter with type build for build output, level error, text or HTTP status_code. When hasMore is true, page with nextStartTime and nextEndTime.
5. Performance: render_get_metrics (cpu, memory, http-requests, http-latency, bandwidth, instance-count, disk-usage, active-connections).
6. Data stores: render_list_postgres, render_get_postgres, render_list_key_value, render_get_key_value. Connection strings and passwords are never fetched.
7. Domains and jobs: render_list_custom_domains, render_list_jobs, render_get_job.

Writes always need the user's confirmation: render_trigger_deploy (new version goes live when the build succeeds), render_rollback_deploy (an earlier version goes live; auto deploys stay on, so the next push can undo it), render_cancel_deploy, render_restart_service (brief interruption), render_suspend_service (the service stops serving traffic), render_resume_service and render_create_job (runs a command against your live environment, for example a migration). Say exactly what will happen and call only after the user agrees.

Secrets: render_list_env_var_keys returns names only. render_get_env_var_value is installed switched off because it returns a value in plain text; turn it on only if the AI really needs one. Nothing here can delete services, databases, domains or variables.

Times are ISO 8601 in UTC, e.g. 2026-10-15T08:00:00Z. Logs and metrics default to the last hour.

Pagination: list answers carry a cursor on every item; call again with cursor set to the last item's cursor until fewer items than limit come back.

Errors: 401 means the API key is wrong or revoked. 403 means the key's user may not do this in that workspace. 404 means a wrong id, or a resource in a workspace the key cannot reach. 429 means the rate limit is reached; wait and retry.

Out of scope here: creating, updating or deleting services, databases, environment groups, domains and environment variables, scaling, blueprints and webhooks.